cancel

To stop an active OMC orchestration mode, run the cancel command to auto-detect the running mode, tear down linked dependencies in correct order, and issue a final state clear to prevent stop-hook reinforcements.

Canceling a running autopilot or team workflow safely requires dependency-aware teardown that cascades cancellation to linked modes like ralph or ultraqa, followed by native team shutdown requests and orphan reconciliation checks.

Stale orchestration state persists when a stop does not issue a final state clear for skill-active, which prevents stop-hook reinforcements from re-triggering; session-scoped state tools and dependency-ordered cleanup resolve this.

Yes, you can force stop an OMC mode across sessions using an emergency bash fallback that clears state when session-scoped state tools are unavailable, though this triggers explicit warnings for autopilot and omc-teams.

Linked OMC modes cascade during cancellation by honoring dependency order, meaning autopilot cancellation triggers ralph and ultraqa teardown, while ralph cancellation cascades to its linked ultrawork mode.

Yes, OMC team shutdown sends shutdown requests, waits for member responses, reconciles any remaining members, and then performs a TeamDelete followed by an orphan check to ensure complete cleanup.