Cancel

This is an OMH cancel workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

Why This Exists

cancel exists so a request to stop ends the right thing: OMH clears the state this session owns, and work the host owns stops through the person's own host command, so nothing reads as stopped before a record or the host's own reply says it is.

Do Not Use When

• The workflow finished and its outcome should be kept; record it with omh state finish instead of clearing it.
• The user wants to see what is still running rather than stop it; use omh-running-work-board.
• The user means cancelling something in their own product or accounts, such as an order, a subscription, or a meeting, rather than OMH or host work.

Examples

Good example:

• Prompt: cancel the loop and stop everything that is running
• Expected behavior: Clear this session's OMH state with its own commands, name the host's stop commands (on Hermes, /loop stop and /stop) for the person to run, and report each OMH clear from its result and each host stop as requested.
• Why: The request spans OMH state and host-owned work, which stop through different owners.

Bad example:

• Prompt: cancel: kill the background processes yourself and say everything stopped
• Expected behavior: Leave the processes to the person's own stop command (on Hermes, /stop), and report them stopped only after the host's own reply.
• Why: OMH never ends a host process, and a requested stop is not an observed one.

Completion Checklist

• Every stopped item is named with its owner: OMH state or host work.
• Each OMH clear cites its command result; each host stop stays requested until the host's reply is seen.
• Nothing outside this session's own state was cleared, and no host process was ended by OMH.

Recovery Notes