// 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.
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.
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.
Guardian service that monitors the active runtime agent's state and automatically restarts it if stopped. Use when checking agent liveness state or understanding the auto-restart mechanism.
Guidelines for managing zylos components via CLI and C4 channels. Use when installing, upgrading, or uninstalling components, or when user asks about available components.
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.
Use when the user asks to restart Claude Code, or after changing settings/hooks/keybindings.
| name | upgrade-claude |
| description | 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. |
Upgrade Claude Code to the latest version - sends /exit, waits for exit, upgrades, and lets activity-monitor restart.
Before launching the upgrade script, complete these steps in order:
Check for running background agents (Task tool). If any are active, stop them to avoid orphaned work.
Update memory files (state.md, sessions/current.md, etc.) to preserve important context that would otherwise be lost on restart.
Write a brief message covering:
Send the full handoff summary to the internal web console channel via C4:
cat <<'EOF' | node ~/zylos/.claude/skills/comm-bridge/scripts/c4-send.js "web-console" "session-handoff"
<handoff summary>
EOF
This records the handoff in C4 conversation history so the upgraded session's
startup hook (c4-session-init) can include it in startup context.
Do not send the full handoff summary to the active external user channel
(Telegram, Lark, Feishu, HXA, etc.). Handoff summaries are operational context
for the next agent session and may contain task state from outside the current
conversation. If the user is actively waiting, send only a short user-facing
notice to their current reply via path, without internal task inventory or
cross-channel context.
IMPORTANT: Must use nohup ... & pattern!
nohup node ~/zylos/.claude/skills/upgrade-claude/scripts/upgrade.js >> ~/zylos/logs/upgrade.log 2>&1 &
/exit into the control queue (priority=1, block_queue_until_idle) — dispatcher handles idle detection and message blockingcurl -fsSL https://claude.ai/install.sh | bash)