Agent skill
upgrade-claude
Upgrade Claude Code to the latest version with graceful shutdown and auto-restart. Use when the user asks to upgrade or when a new Claude Code version is available.
Install this agent skill to your Project
npx add-skill https://github.com/zylos-ai/zylos-core/tree/main/skills/upgrade-claude
SKILL.md
Upgrade Claude Code Skill
Upgrade Claude Code to the latest version - sends /exit, waits for exit, upgrades, and lets activity-monitor restart.
When to Use
- User explicitly asks to upgrade Claude Code
- New Claude Code version is available
- Need to apply Claude Code updates
Pre-Upgrade Checklist
Before launching the upgrade script, complete these steps in order:
1. Stop background tasks
Check for running background agents (Task tool). If any are active, stop them to avoid orphaned work.
2. Sync memory
Update memory files (state.md, sessions/current.md, etc.) to preserve important context that would otherwise be lost on restart.
3. Write a session handoff summary
Write a brief message covering:
- What was being worked on (active tasks, user requests in progress)
- Current state (what's done, what's pending, any blockers)
- What the next session should pick up (if anything)
4. Send the handoff summary
Determine who to notify:
- If actively collaborating with a user: Send the summary to that user's channel via C4 (their
reply viapath). This keeps the user informed AND records the context into C4 conversation history. - If no active user conversation: Send the summary to the web console channel. This still records it into C4 so the new session's startup hook (c4-session-init) will include it in the conversation context.
The goal is twofold: (a) the user knows what's happening, and (b) the handoff summary appears in C4 conversation history, so the new session can seamlessly continue the work.
5. Launch the upgrade script
IMPORTANT: Must use nohup ... & pattern!
nohup node ~/zylos/.claude/skills/upgrade-claude/scripts/upgrade.js >> ~/zylos/logs/upgrade.log 2>&1 &
How It Works
- Enqueue /exit: Puts
/exitinto the control queue (priority=1, block_queue_until_idle) — dispatcher handles idle detection and message blocking - Wait for exit: Monitors Claude process until it exits (up to 120s); aborts if timeout
- Upgrade: Runs native installer (
curl -fsSL https://claude.ai/install.sh | bash) - Daemon restart: activity-monitor detects exit and restarts Claude automatically
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
web-console
Built-in web interface for communicating with Claude without external services. Use when setting up or configuring the web console channel, or troubleshooting browser-based access.
component-management
Guidelines for managing zylos components via CLI and C4 channels. Use when installing, upgrading, or uninstalling components, or when user asks about available components.
restart-claude
Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings.
comm-bridge
C4 communication bridge — central gateway for ALL external communication (Telegram, Lark, etc.). Use when replying to users via the "reply via" path, sending proactive messages to external channels, querying recent conversations or checkpoint status (prefer c4-db.js CLI; sqlite3 OK for unsupported queries), fetching conversation history for Memory Sync, or creating checkpoints after sync. Incoming messages are queued by channel bots and delivered to Claude via a PM2 dispatcher daemon. Session-start hooks automatically provide conversation context and can trigger Memory Sync when unsummarized conversations exceed the configured threshold.
new-session
Start a new session when context is high. Claude uses /clear, Codex uses /exit. Use when context is high or when a fresh session is needed.
http
Caddy-based web server providing web console hosting, file sharing, and health check endpoints. Use when configuring HTTP access, setting up file sharing, or troubleshooting web connectivity.
Didn't find tool you were looking for?