update

Detects new versions of Claude Code and ClawCode and prints safe update commands.

62|14|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/crisandrews/ClawCode --skill update-crisandrews
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/crisandrews/ClawCode/tree/main/skills/update
Command: npx skills add https://github.com/crisandrews/ClawCode --skill update-crisandrews

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude Code's built-in auto-updater is disabled when ClawCode runs as a long-running daemon, so users have no way to know when new versions of Claude Code or ClawCode are available or how to apply them safely. ## Core Features & Use Cases - Version Detection: Compares the installed Claude Code binary against the latest npm release and the local ClawCode checkout against upstream git tags. - Safe Update Guidance: Prints the exact commands (npm install, git pull, systemctl restart) without executing them, since the agent user typically lacks root permissions. - Silent Heartbeat Mode: Deduplicates notifications via a memory-backed file so each new version is announced exactly once, with a 24-hour network check throttle. - Use Case: A user running ClawCode as a systemd user service asks "check for updates" and receives a status block showing current versus available versions plus the commands to apply them. ## Quick Start Ask the agent to check for updates by saying "check for updates" or invoking /agent:update.

Frequently Asked Questions about update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for Claude Code updates when the auto-updater is disabled?

Run the update skill, which compares the installed claude binary version against the latest @anthropic-ai/claude-code release on npm. It prints the safe install command but never executes it, since global npm installs typically require root.

How do I update the ClawCode plugin to the latest release?

The skill fetches upstream tags and compares them to your local checkout. If a newer release tag exists, it tells you to run git pull upstream main in the plugin directory, then restart the systemd user service.

Does the update skill apply updates automatically?

No. It only detects and reports updates, then prints the commands for the user to run. This is deliberate, because a daemonized agent auto-updating its own runtime is unsafe, and the claude user usually lacks permission for global npm installs.

Why does the skill ignore plain commits on upstream main?

Only new release tags trigger an update notification. Routine chore, docs, or CI commits on upstream main do not count, so users are not trained to ignore update pings from constant low-value notifications.

How does the heartbeat avoid notifying about the same version repeatedly?

A memory-backed JSON file records the last-notified version for each component. The skill only pings when the available version differs from both the installed and last-notified versions, and network checks are throttled to once per 24 hours.