Stop an active OMX workflow after identifying its session and related modes. Perform the required cleanup, preserve resumable state where specified, and report the outcome, including any cleanup failures or reasons for refusing to proceed.
Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team)
Review the instructions the agent will receive before you install.
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.
/cancel and /cancel --force.--all, unknown flags, repeated flags, and mixed flags before mutation.omx state list-active --json
omx state get-status --mode <mode> --json
autopilot → ralph → ultrawork → ecomode → ultraqa → swarm → ultrapilot → pipeline → team → plan-consensus.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.omx team status <team> --json; use omx team shutdown <team> after the normal completion gate, or follow the explicit abort path.omx state clear --input '{"mode":"<mode>","session_id":"<session>"}' --json
--force, perform its documented native-stop cleanup. Report rollback or cleanup failures rather than claiming success.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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.
Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.
Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.
Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.
Run a persistent research workflow with a defined goal and explicit acceptance checks. It saves progress and finishes only when a recorded result passes either a validation script or an architect review of the research output.
Find the replacement for a research command removed in OMX 0.21. This migration notice directs existing autoresearch-goal usage to $autoresearch, the canonical research loop that requires validation before proceeding.