cancel

To cancel an active OMC mode and perform state cleanup, use the cancel skill. It detects the active mode, executes mode-specific cancellation, and clears the skill-active state to prevent lingering processes.

The best way to stop autopilot or ultrawork across all sessions is using the global force cleanup. Running cancel with the --force or --all option executes a global cleanup across all active sessions.

Your OMC stop hook keeps re-triggering because the skill-active state was not cleared. The cancel skill ensures final cleanup by always clearing the skill-active state to prevent this re-triggering behavior.

You can gracefully cancel pipeline or swarm modes without leaving lingering processes by using the cancel skill. It performs dependency-aware cancellation that stops the active mode and cleans related state automatically.

You need to use force cancellation for OMC workflow cleanup when multiple sessions are active. The default cancel operation works per session, while the --force or --all flags enable global cleanup across all sessions.