Cancel Skill

SkillDev tools

The cancel skill is a dev-tools skill that cancels any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team). It validates the request, checks which modes are running through the omx state commands, then clears each mode's state in dependency order. It preserves resumable state where possible, cleans up linked child modes, shuts down teams through their own command, and refuses to

Available today. Use it from your connected AI after setup.

Have the cancel skill available and read AGENTS.md#durable-runtime-invariants-canonical-ssot for scope, ownership, hooks, and Team cleanup rules.

Then ask your AI: use the Cancel Skill skill

What your AI can do with it

  • Cancel an active OMX mode such as autopilot, ralph, ultrawork, or team
  • Inspect running modes with omx state list-active --json and omx state get-status
  • Clear a selected mode's state with omx state clear
  • Preserve resumable state and clean up linked child modes
  • Shut down a team with omx team status and omx team shutdown
  • Refuse to act when session or target evidence is missing

Getting started

  1. Have the cancel skill available and read AGENTS.md#durable-runtime-invariants-canonical-ssot for scope, ownership, hooks, and Team cleanup rules.
  2. Run /cancel, or /cancel --force for its documented native-stop cleanup; other flags such as --all are rejected.
  3. Discover the current session or root with omx state list-active --json and omx state get-status --mode <mode> --json.
  4. Confirm the current session/root and exact target before cleanup, and stop if the required evidence is missing.
  5. Clear only the selected mode or session state through the state API, for example omx state clear --input '{"mode":"<mode>","session_id":"<session>"}' --json.

What this skill tells your AI

The instructions your AI receives, as published by yeachan-heo/oh-my-codex in skills/cancel/SKILL.md and read by ahel’s review.

When to use

Use /cancel (or cancelomc / stopomc) to stop an active OMX mode and perform its documented cleanup. Read AGENTS.md#durable-runtime-invariants-canonical-ssot first; it is the invariant authority for scope, ownership, hooks, and Team cleanup.

Inputs and preconditions

  • Accepted forms are /cancel and /cancel --force.
  • Reject --all, unknown flags, repeated flags, and mixed flags before mutation.
  • Discover the current session/root with the state read surfaces before cleanup:
    omx state list-active --json
    omx state get-status --mode <mode> --json
    
  • Confirm the current session/root and exact target before cleanup; stop when the required evidence is missing.

Operational steps

  1. Parse and validate arguments; select one exact session/root scope.
  2. Inspect active modes in dependency order: autopilot → ralph → ultrawork → ecomode → ultraqa → swarm → ultrapilot → pipeline → team → plan-consensus.
  3. Cancel Autopilot while preserving its resumable state; clean only linked child modes it owns.
  4. For Ralph, terminalize the target state (active:false, current_phase:"cancelled", completed_at) and terminalize a proven linked Ultrawork/Ecomode state in the same scope. Confirm the post-conditions in docs/contracts/ralph-cancel-contract.md.
  5. Clear standalone modes only after proving they are not linked to another active mode.
  6. For Team, inspect the runtime with omx team status <team> --json; use omx team shutdown <team> after the normal completion gate, or follow the explicit abort path.
  7. Clear only the selected mode/session state through the state API, for example:
    omx state clear --input '{"mode":"<mode>","session_id":"<session>"}' --json
    
  8. With --force, perform its documented native-stop cleanup. Report rollback or cleanup failures rather than claiming success.

Exit and evidence

Report one result per selected mode: mode, scope/session, terminal phase, preserved state, linked cleanup, and any refusal reason. A clean no-op reports No active OMX modes detected. Include Team status and shutdown evidence when Team was selected.

Signals

GitHub stars
33k
Forks
3k
Last commit
Oct 2026
Hacker News mentions
20

Questions

What does the cancel skill do?
It stops an active OMX mode and performs its documented cleanup, checking running modes with the omx state commands and clearing each mode's state in dependency order.
Which modes can it cancel?
Autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team.
Advanced
Item type
skill
Key
cancel-2
Source
github.com/yeachan-heo/oh-my-codex