2.6k Downloads
Overview
Periodically checks GitHub for new clawdbot releases and notifies the user once per new version, avoiding repeated or spammy alerts.
Key Advantages
1.Purpose-built for clawdbot users to stay current with releases without manual checking
2.One-time-per-version notification logic prevents nagging and alert fatigue
3.Simple cron-based scheduling script for hands-off daily checks
4.Supports Telegram notifications for push-style alerts at chosen times
5.Caching of GitHub responses reduces API calls and improves performance/reliability under rate limits
Use Cases
- Automatically notifying a clawdbot operator when a new release is available, once per version
- Daily scheduled release checks via cron on a development or production host
- Providing remote Telegram alerts about clawdbot updates for maintainers on the go
- Reviewing how many versions behind a deployment is and what key highlights were missed
- Forcing a refresh and re-notification when deliberately re-evaluating an upgrade path
Evaluation Scores
8.1
/ 10
Reliability
7.8
Functionality
8.0
Usability
7.9
Safety
9.2
Performance
8.8
Compatibility
6.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.1/103/19/2026▼
OS: linux-arm64LLM: anthropic/claude-sonnet-4.6
**Verdict:** A focused, well-scoped utility for clawdbot operators who want reliable, non-spammy release notifications, especially useful when combined with cron and Telegram. It is not a general-purpose update checker and is tightly coupled to clawdbot and a Unix-like environment.
**Strengths:**
- Clean single-purpose design: checks `github.com/clawdbot/clawdbot/releases`, compares to local `package.json`, and notifies once per version.
- Sensible state and cache handling (`~/.clawdbot/*-state.json`, `*-cache.json`) to avoid repeated alerts and unnecessary GitHub calls.
- Clear CLI interface and examples (`check.sh --status`, `--force`, `--all-highlights`, `--reset`, `--help`).
- Cron setup helper script with Telegram integration for scheduled, push-style notifications.
**Risks & Limitations:**
- Narrow scope: only useful if you are running clawdbot; no value for other skills or services.
- Environment assumptions: relies on shell scripts, cron, and `launchctl` (macOS-oriented), so not ideal for Windows or non-standard setups.
- External dependency on GitHub availability and API behavior; network or API changes could affect reliability.
- Requires basic CLI and system configuration comfort (cron, environment variables, gateway restart) to get full value.
**Best suited for:**
- Developers or operators running clawdbot in a Unix-like environment who want a “set and forget” update alert system.
- Teams that want lightweight release visibility (including missed-release highlights) without integrating a heavier monitoring or CI solution.
- Power users who prefer push notifications (e.g., via Telegram) over manually checking GitHub or package versions.
Comments (0)
No comments yet. Be the first!