cancel
End any active OMX execution mode — autopilot, ralph, ultrawork, team, or ultraqa — and optionally clear all session state.
cancel is the clean exit for OMX execution modes. When autopilot, ralph, ultrawork, team, or ultraqa is running, cancel signals the active mode to stop, completes any in-flight writes, and returns control to you. With the --force flag it also wipes all session state so the next command starts fresh.
Purpose
Long-running OMX modes accumulate state: plans, context snapshots, team task lists, and loop counters. cancel gives you a predictable, safe way to exit those modes without leaving orphaned state or half-written files behind. Use it when a task is done and verified, when you want to redirect effort, or when a loop is blocked.
How to invoke
Natural language triggers: "cancel", "stop", "halt", "exit autopilot", "stop ralph".
Explicit slash: $cancel
codex
> cancelcodex
> cancel --forceWhat it does
- Detects which execution mode is currently active (autopilot, ralph, ultrawork, team, ultraqa)
- Signals the mode to stop at the next safe checkpoint
- Waits for any in-flight file writes or agent completions before exiting
- Clears active mode state from
.omx/state/ - With
--force: removes all session state including plans, context snapshots, and task lists
Outputs
- Confirmation that the active mode has exited
- With
--force: confirmation that.omx/state/has been cleared - No source code changes
Related
$hud— check which mode is active before cancelling$ralph— ralph exits cleanly via cancel when its loop is satisfied$autopilot— the primary mode cancel is used to stop