Cancel any active OMC mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline)
npxskills add yeachan-heo/oh-my-claudecode--skill cancelLoading…
Intelligent cancellation that detects and cancels the active OMC mode.
The cancel skill is the standard way to complete and exit any OMC mode.
When the stop hook detects work is complete, it instructs the LLM to invoke
this skill for proper state cleanup. If cancel fails or is interrupted,
retry with --force flag, or wait for the 2-hour staleness timeout as
a last resort.
Automatically detects which mode is active and cancels it:
/oh-my-claudecode:cancel
Or say: "cancelomc", "stopomc"
The state management tools (state_clear, state_read, state_write, state_list_active,
state_get_status) may be registered as deferred tools by Claude Code. Before calling
any state tool, you MUST first load all of them via ToolSearch:
ToolSearch(query="select:mcp__plugin_oh-my-claudecode_t__state_clear,mcp__plugin_oh-my-claudecode_t__state_read,mcp__plugin_oh-my-claudecode_t__state_write,mcp__plugin_oh-my-claudecode_t__state_list_active,mcp__plugin_oh-my-claudecode_t__state_get_status")
If state_clear is unavailable or fails, use this bash fallback as an emergency
escape from the stop hook loop. This is NOT a full replacement for the cancel flow —
it only removes state files to unblock the session. Linked modes (e.g. ralph→ultrawork,
autopilot→ralph/ultraqa) must be cleared separately by running the fallback once per mode.
Replace MODE with the specific mode (e.g. ralplan, ralph, ultrawork, ultraqa).
WARNING: Do NOT use this fallback for autopilot or omc-teams. Autopilot requires
state_write(active=false) to preserve resume data. omc-teams requires tmux session
cleanup that cannot be done via file deletion alone.
# Fallback: direct file removal when state_clear MCP tool is unavailable
SESSION_ID="${CLAUDE_SESSION_ID:-${CLAUDECODE_SESSION_ID:-}}"
REPO_ROOT="$(git rev-parse --show-toplevel 2>/dev/null || { d="$PWD"; while [ "$d" != "/" ] && [ ! -d "$d/.omc" ]; do d="$(dirname "$d")"; done; echo "$d"; })"
# Cross-platform SHA-256 (macOS: shasum, Linux: sha256sum)
sha256portable() { printf '%s' "$1" | (sha256sum 2>/dev/null || shasum -a 256) | cut -c1-16; }
# Resolve state directory (supports OMC_STATE_DIR centralized storage)
if [ -n "${OMC_STATE_DIR:-}" ]; then
# Mirror getProjectIdentifier() from worktree-paths.ts
SOURCE="$(git remote get-url origin 2>/dev/null || echo "$REPO_ROOT")"
HASH="$(sha256portable "$SOURCE")"
DIR_NAME="$(basename "$REPO_ROOT" | sed 's/[^a-zA-Z0-9_-]/_/g')"
OMC_STATE="$OMC_STATE_DIR/${DIR_NAME}-${HASH}/state"
[ ! -d "$OMC_STATE" ] && { echo "ERROR: State dir not found at $OMC_STATE" >&2; exit 1; }
elif [ "$REPO_ROOT" != "/" ] && [ -d "$REPO_ROOT/.omc" ]; then
OMC_STATE="$REPO_ROOT/.omc/state"
else
echo "ERROR: Could not locate .omc state directory" >&2
exit 1
fi
MODE="ralplan" # <-- replace with the target mode
# Clear session-scoped state for the specific mode
if [ -n "$SESSION_ID" ] && [ -d "$OMC_STATE/sessions/$SESSION_ID" ]; then
rm -f "$OMC_STATE/sessions/$SESSION_ID/${MODE}-state.json"
rm -f "$OMC_STATE/sessions/$SESSION_ID/${MODE}-stop-breaker.json"
rm -f "$OMC_STATE/sessions/$SESSION_ID/skill-active-state.json"
# Write cancel signal so stop hook detects cancellation in progress
NOW_ISO="$(date -u +"%Y-%m-%dT%H:%M:%SZ")"
EXPIRES_ISO="$(date -u -d "+30 seconds" +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || python3 - <<'PY'\nfrom datetime import datetime, timedelta, timezone\nprint((datetime.now(timezone.utc) + timedelta(seconds=30)).strftime('%Y-%m-%dT%H:%M:%SZ'))\nPY\n)"
printf '{"active":true,"requested_at":"%s","expires_at":"%s","mode":"%s","source":"bash_fallback"}' \
"$NOW_ISO" "$EXPIRES_ISO" "$MODE" > "$OMC_STATE/sessions/$SESSION_ID/cancel-signal-state.json"
fi
# Clear legacy state only if no session ID (avoid clearing another session's state)
if [ -z "$SESSION_ID" ]; then
rm -f "$OMC_STATE/${MODE}-state.json"
fi
/oh-my-claudecode:cancel follows the session-aware state contract:
state_list_active and state_get_status, navigating .omc/state/sessions/{sessionId}/… to discover which mode is active..omc/state/*.json are consulted only as a compatibility fallback if the session id is missing or empty..omc/state/swarm.db / .omc/state/swarm-active.marker) and is not session-scoped.state_clear with the session id to remove only the matching session files; modes stay bound to their originating session.Active modes are still cancelled in dependency order:
<self-improve-root>/state/agent-settings.json; new runs use .omc/self-improve/topics/<topic-slug>/, with flat .omc/self-improve/ retained only for legacy single-track resumes)Use --force or --all when you need to erase every session plus legacy artifacts, e.g., to reset the workspace entirely.
/oh-my-claudecode:cancel --force
/oh-my-claudecode:cancel --all
Steps under the hood:
state_list_active enumerates .omc/state/sessions/{sessionId}/… to find every known session.state_clear runs once per session to drop that session’s files.state_clear without session_id removes legacy files under .omc/state/*.json, .omc/state/swarm*.db, and compatibility artifacts (see list).~/.claude/teams/*/, ~/.claude/tasks/*/, .omc/state/team-state.json) are best-effort cleared as part of the legacy fallback.
Every state_clear command honors the session_id argument, so even force mode still uses the session-aware paths first before deleting legacy files.
Legacy compatibility list (removed only under --force/--all):
.omc/state/autopilot-state.json.omc/state/ralph-state.json.omc/state/ralph-plan-state.json.omc/state/ralph-verification.json.omc/state/ultrawork-state.json.omc/state/ultraqa-state.json.omc/state/swarm.db.omc/state/swarm.db-wal.omc/state/swarm.db-shm.omc/state/swarm-active.marker.omc/state/swarm-tasks.db.omc/state/ultrapilot-state.json.omc/state/ultrapilot-ownership.json.omc/state/pipeline-state.json.omc/state/omc-teams-state.json.omc/state/plan-consensus.json.omc/state/ralplan-state.json.omc/state/boulder.json.omc/state/hud-state.json.omc/state/subagent-tracking.json.omc/state/subagent-tracker.lock.omc/state/rate-limit-daemon.pid.omc/state/rate-limit-daemon.log.omc/state/checkpoints/ (directory).omc/state/sessions/ (empty directory cleanup after clearing sessions)When you invoke this skill:
# Check for --force or --all flags
FORCE_MODE=false
if [[ "$*" == *"--force"* ]] || [[ "$*" == *"--all"* ]]; then
FORCE_MODE=true
fi
The skill now relies on the session-aware state contract rather than hard-coded file paths:
state_list_active to enumerate .omc/state/sessions/{sessionId}/… and discover every active session.state_get_status to learn which mode is running (autopilot, ralph, ultrawork, etc.) and whether dependent modes exist.session_id was supplied to /oh-my-claudecode:cancel, skip legacy fallback entirely and operate solely within that session path; otherwise, consult legacy files in .omc/state/*.json only if the state tools report no active session. Swarm remains a shared SQLite/marker mode outside session scoping.Use force mode to clear every session plus legacy artifacts via state_clear. Direct file removal is reserved for legacy cleanup when the state tools report no active sessions.
Teams are detected through OMC team state, not removed Claude Code ~/.claude/teams config directories:
# Check for active OMC team state
state_read(mode="team")
Two-pass cancellation protocol:
Pass 1: Graceful Shutdown
For the active OMC team state:
1. Read team_name and worker labels from OMC state/handoffs/task bookkeeping
2. For each active teammate:
a. Ask or notify the named teammate through the active conversation/team messaging surface
b. Wait up to 15 seconds for shutdown_response
c. If response received: mark member acknowledged
d. If timeout: mark member as unresponsive, continue to next
3. Log: "Graceful pass: X/Y members responded"
Pass 2: Reconciliation
After graceful pass:
1. Wait 5 more seconds for unresponsive teammates that may still be processing
2. Record any remaining unresponsive teammates in the cancellation report
3. Do not call TeamDelete; Claude Code 2.1.178+ removed per-team native cleanup
OMC State Cleanup:
1. Clear team state: state_clear(mode="team")
2. Check for linked ralph: state_read(mode="ralph") — if linked_team is true:
a. Clear ralph state: state_clear(mode="ralph")
b. Clear linked ultrawork if present: state_clear(mode="ultrawork")
3. Run OMC tmux/CLI orphan scan only for legacy `omc team` / `/omc-teams` workers (see below)
4. Emit structured cancel report
Orphan Detection (Post-Cleanup):
For legacy OMC tmux/CLI worker runs, verify no worker processes remain:
node "${CLAUDE_PLUGIN_ROOT}/scripts/cleanup-orphans.mjs" --team-name "{team_name}"
The orphan scanner:
ps aux (Unix) or tasklist (Windows) for OMC worker processes with --team-name matching the cleaned-up teamUse --dry-run to inspect without killing. The scanner is safe to run multiple times.
Structured Cancel Report:
Team "{team_name}" cancelled:
- Members signaled: N
- Responses received: M
- Unresponsive: K (list names if any)
- OMC state cleared: yes/no
- Manual cleanup needed: yes/no
Path: OMC team state / tmux worker processes, if any
Implementation note: The cancel skill is executed by the LLM, not as a bash script. When you detect an active team:
state_read(mode="team") to find the active OMC teamstate_clear(mode="team", session_id)Autopilot handles its own cleanup including linked ralph and ultraqa.
state_read(mode="autopilot", session_id) to get current phasestate_read(mode="ralph", session_id):
linked_ultrawork: true, clear ultrawork first: state_clear(mode="ultrawork", session_id)state_clear(mode="ralph", session_id)state_read(mode="ultraqa", session_id):
state_clear(mode="ultraqa", session_id)state_write(mode="autopilot", session_id, state={active: false, ...existing})state_read(mode="ralph", session_id) to check for linked ultraworklinked_ultrawork: true:
linked_to_ralph: truestate_clear(mode="ultrawork", session_id)state_clear(mode="ralph", session_id)state_read(mode="ultrawork", session_id)linked_to_ralph: true, warn user to cancel ralph instead (which cascades)state_clear(mode="ultrawork", session_id)Clear directly: state_clear(mode="ultraqa", session_id)
Report: "No active OMC modes detected. Use --force to clear all state files anyway."
The cancel skill runs as follows:
--force / --all flags, tracking whether cleanup should span every session or stay scoped to the current session id.state_list_active to enumerate known session ids and state_get_status to learn the active mode (autopilot, ralph, ultrawork, etc.) for each session.state_clear with that session_id to remove only the session’s files, then run mode-specific cleanup (autopilot → ralph → …) based on the state tool signals.state_clear per session, then run a global state_clear without session_id to drop legacy files (.omc/state/*.json, compatibility artifacts) and report success. Swarm remains a shared SQLite/marker mode outside session scoping.~/.claude/teams/*/, ~/.claude/tasks/*/, .omc/state/team-state.json) remain best-effort cleanup items invoked during the legacy/global pass.--force was used:
state_clear(mode="skill-active", session_id)
skill-active-state.json. See issue #2118.State tools always honor the session_id argument, so even force mode still clears the session-scoped paths before deleting compatibility-only legacy state.
Mode-specific subsections below describe what extra cleanup each handler performs after the state-wide operations finish.
| Mode | Success Message |
|---|---|
| Autopilot | "Autopilot cancelled at phase: {phase}. Progress preserved for resume." |
| Ralph | "Ralph cancelled. Persistent mode deactivated." |
| Ultrawork | "Ultrawork cancelled. Parallel execution mode deactivated." |
| UltraQA | "UltraQA cancelled. QA cycling workflow stopped." |
| Swarm | "Swarm cancelled. Coordinated agents stopped." |
| Ultrapilot | "Ultrapilot cancelled. Parallel autopilot workers stopped." |
| Pipeline | "Pipeline cancelled. Sequential agent chain stopped." |
| Team | "Team cancelled. Teammates shut down and cleaned up." |
| Plan Consensus | "Plan Consensus cancelled. Planning session ended." |
| Force | "All OMC modes cleared. You are free to start fresh." |
| None | "No active OMC modes detected." |
| Mode | State Preserved | Resume Command |
|---|---|---|
| Autopilot | Yes (phase, files, spec, plan, verdicts) | /oh-my-claudecode:autopilot |
| Ralph | No | N/A |
| Ultrawork | No | N/A |
| UltraQA | No | N/A |
| Swarm | No | N/A |
| Ultrapilot | No | N/A |
| Pipeline | No | N/A |
| Plan Consensus | Yes (plan file path preserved) | N/A |
.omc/state/ directoryWhen cancelling modes that may have spawned MCP workers (team bridge daemons), the cancel skill should also:
.omc/state/team-bridge/{team}/*.heartbeat.jsontmux kill-session -t omc-team-{team}-{worker} for each worker.omc/state/team-mcp-workers.jsonWhen --force is used, also clean up:
rm -rf .omc/state/team-bridge/ # Heartbeat files
rm -f .omc/state/team-mcp-workers.json # Shadow registry
# Kill all omc-team-* tmux sessions
tmux list-sessions -F '#{session_name}' 2>/dev/null | grep '^omc-team-' | while read s; do tmux kill-session -t "$s" 2>/dev/null; done
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).