clawdbot-release-check
Check for new clawdbot releases and notify once per new version.
When & Why to Use This Skill
The clawdbot-release-check skill is a specialized automation utility designed to streamline software maintenance by monitoring GitHub for new Clawdbot releases. It eliminates the need for manual version checking by comparing local installations with the latest remote tags, providing concise release highlights and delivering notifications through integrated channels like Telegram. This ensures developers and system administrators stay informed about critical bug fixes and new features with minimal noise.
Use Cases
- Automated Update Monitoring: Configure a system-level cron job to perform daily checks for new software versions, ensuring your development environment remains up-to-date automatically.
- Release Highlight Summarization: Receive instant summaries of new features and breaking changes directly in your terminal or notification app, bypassing the need to manually browse GitHub release pages.
- Remote Notification Integration: Connect the update checker to Telegram to receive real-time alerts on your mobile device whenever a new version of Clawdbot is published.
- Environment Version Auditing: Use the status command to quickly verify if local deployments are lagging behind the latest stable release across multiple machines.
| name | clawdbot-release-check |
|---|---|
| description | Check for new clawdbot releases and notify once per new version. |
| homepage | https://github.com/clawdbot/clawdbot |
| metadata | {"clawdbot":{"emoji":"🔄","requires":{"bins":["curl","jq"]}}} |
Clawdbot Release Check
Checks for new clawdbot releases from GitHub and notifies you once per version. No nagging.
Installation
clawdhub install clawdbot-release-check
Quick Setup (with cron)
# Add daily update check at 9am, notify via Telegram
{baseDir}/scripts/setup.sh --telegram YOUR_TELEGRAM_ID
# Custom hour (e.g., 8am)
{baseDir}/scripts/setup.sh --hour 8 --telegram YOUR_TELEGRAM_ID
# Remove cron job
{baseDir}/scripts/setup.sh --uninstall
After setup, restart the gateway:
launchctl kickstart -k gui/$(id -u)/com.clawdis.gateway
Manual Usage
# Check for updates (silent if up-to-date or already notified)
{baseDir}/scripts/check.sh
# Show version info
{baseDir}/scripts/check.sh --status
# Force notification (bypass "already notified" state)
{baseDir}/scripts/check.sh --force
# Show highlights from ALL missed releases
{baseDir}/scripts/check.sh --all-highlights
# Clear state (will notify again on next check)
{baseDir}/scripts/check.sh --reset
# Help
{baseDir}/scripts/check.sh --help
How It Works
- Fetches latest release from
github.com/clawdbot/clawdbot/releases - Compares with your installed version (from
package.json) - If behind, shows highlights from release notes
- Saves state to prevent repeat notifications
Example Output
🔄 **Clawdbot Update Available!**
Current: `2.0.0-beta5`
Latest: `2026.1.5-3`
_(3 versions behind)_
**Highlights:**
- Models: add image-specific model config
- Agent tools: new `image` tool
- Config: default model shorthands
🔗 https://github.com/clawdbot/clawdbot/releases/tag/v2026.1.5-3
To update: `cd /path/to/clawdis && git pull && pnpm install && pnpm build`
Files
State — ~/.clawdbot/clawdbot-release-check-state.json:
{
"lastNotifiedVersion": "v2026.1.5-3",
"lastCheckMs": 1704567890123
}
Cache — ~/.clawdbot/clawdbot-release-check-cache.json:
- Release data cached for 24 hours (saves API calls)
- Highlights extracted once per release (saves tokens)
- Use
--clear-cacheto force refresh
Configuration
Environment variables:
CLAWDBOT_DIR— Path to clawdbot source (auto-detected from~/dev/clawdis,~/clawdbot, or npm global)CACHE_MAX_AGE_HOURS— Cache TTL in hours (default: 24)