Skip to content

Guide · Agent skill

How to use the Cancel Active OMC Modes agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The cancel skill is an agent skill for the oh-my-claudecode (OMC) plugin that stops or finishes a running OMC mode, such as autopilot, ralph, swarm or team, and clears that mode's saved state. It is for developers who already use the OMC plugin and need to exit a stuck or finished run. After this guide you will know what the skill does, how to install it, how to trigger it with plain requests, and which flags are safe to use. If you have never used agent skills: a skill is a folder with a SKILL.md file that tells an AI agent how to perform a specific task. The agent loads it when a request matches. This skill only does something useful when the oh-my-claudecode plugin is installed.

Cancel Active OMC ModesYeachan-Heo/oh-my-claudecode · MIT

Quick start

  1. 1Install oh-my-claudecode. Make sure the oh-my-claudecode plugin is installed, since the cancel skill only works inside its mode system.
  2. 2Download and unzip the skill. Download the ZIP from this page and unzip it to get the folder containing SKILL.md.
  3. 3Place the skill folder. Move it into ~/.claude/skills/ for personal use or .claude/skills/ in a project, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
  4. 4Run the default cancel. Ask the agent to cancel or type /oh-my-claudecode:cancel to stop the active mode in the current session.
  5. 5Escalate only if needed. If shutdown is stuck, try --force for the current session. Use --all only when you intend to cancel every known session.

What the cancel skill makes the agent do

When a mode finishes or gets stuck, the agent uses this skill to detect which OMC mode is active, cancel it, and clean up its state. The skill is described as the standard way to complete and exit any OMC mode. The stop hook can also instruct the agent to invoke it for state cleanup once it detects completion.

Autopilot stops the workflow but keeps progress so it can resume. Ralph stops its persistence loop. Swarm stops coordinated agents and releases claimed tasks. Team shuts down gracefully, then clears session-scoped Team state. Ultragoal clears its runtime guard but keeps its plan and ledger files in .omc/ultragoal/.

Install the cancel skill

Download the skill ZIP from this page and unzip it. Then place the folder in one of two locations: ~/.claude/skills/ for all your projects, or .claude/skills/ inside a single project.

Alternatively, in the Claude apps go to Settings, then Capabilities, then Skills, and upload the ZIP there.

  • Personal install: ~/.claude/skills/
  • Project install: .claude/skills/ in your project folder
  • Claude apps: Settings → Capabilities → Skills

Trigger the skill with natural requests

You can run the skill as a slash command or ask for it in plain words. The source lists the phrases cancelomc and stopomc as ways to trigger it.

Use the default command first. Add flags only when you need a stronger or wider cancellation.

  • Slash command: /oh-my-claudecode:cancel
  • Force cancel the current session: /oh-my-claudecode:cancel --force
  • Cancel across all known sessions: /oh-my-claudecode:cancel --all
  • Say: cancelomc or stopomc
/oh-my-claudecode:cancel

Understand the flags

Flags control two separate things: which sessions are affected and how urgently shutdown happens. With no flags, only the current session is cancelled and teammates get a graceful shutdown wait.

--force skips graceful waits but still uses the protected state tools and honours locks and ownership checks. --all reaches every known session, cancelling each one independently. --force --all combines both. The skill says --force never widens scope, and --all is the only cross-session authorization.

  • no flags: current session, graceful
  • --force: current session, forced, skips waits
  • --all: every known session, graceful for each
  • --force --all: every known session, forced

Know what the skill needs

The skill needs the oh-my-claudecode plugin installed and Claude Code with the OMC state tools: state_clear, state_read, state_write, state_list_active and state_get_status. These may be deferred, so the skill loads them with ToolSearch before use. It also needs bash, git, and sha256sum or shasum for the emergency fallback script.

If a state tool is unavailable or fails, the skill retries the same scoped operation and reports the failure.

  • oh-my-claudecode plugin installed
  • Claude Code with OMC state tools
  • bash and git
  • sha256sum or shasum (for the fallback)

Safety notes: scripts and the emergency fallback

This skill runs scripts. It does not use the network, according to its listing. The bundled emergency fallback deletes state files directly for one identified current session. It is only meant to escape a stop-hook loop for a non-force, non-Team cancellation. The skill says not to use it for autopilot, team, omc-teams, for --force or --all, or to bypass a lock, ownership check, corruption or another state-tool failure.

Because --force and the fallback can discard state, run the default command first. Keep in-progress work safe by not using --all unless you mean to cancel every session.

  • Runs scripts: yes. Uses network: no.
  • Fallback removes files only for the identified current session.
  • Use the default command before --force or --all.

Tips for a clean cancellation

If you run several OMC sessions, make sure the session identity is clear. Without one, the skill fails closed for the default command and --force rather than guessing.

When several modes are active, the skill follows a fixed order: autopilot first, then standalone ralph, then retired modes, ultragoal, swarm, ultrapilot and pipeline, team, and finally plan consensus and self-improve. Ralph linked to Team is cleared only after Team succeeds.

  • Start with no flags.
  • Check which session you are in before using --all.
  • Linked Team and Ralph are cancelled in a set order.

What people use it for

  • Exit a finished autopilot run while keeping its progress for resume.
  • Stop a ralph persistence loop that will not end.
  • Shut down a stuck team run and clear its session-scoped state.
  • Cancel one OMC session while leaving others running.

Frequently asked questions

How do I install the cancel skill?

Download the skill ZIP from this page and unzip it. Place the folder in ~/.claude/skills/ for all projects or in .claude/skills/ inside one project. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.

Do I need oh-my-claudecode to use this skill?

Yes. The skill only works inside the oh-my-claudecode plugin's mode system and does nothing useful on its own. You also need Claude Code with the OMC state tools.

Is the cancel skill free?

The source lists the licence as MIT. It does not mention pricing, so check the licence file in the repository for the terms.

What is the difference between --force and --all?

--force skips graceful waits but stays in the current session. --all cancels every known session, each independently. The skill states that --force never widens scope and --all is the only cross-session authorization.

Can this skill delete my work in progress?

It can. --force and the emergency fallback can discard state, and --all reaches across sessions. Use the default command first to keep in-progress work safe.

Why does the skill say it needs ToolSearch?

The OMC state tools may be deferred by Claude Code. The skill loads them with ToolSearch before calling them, and if a state tool fails it retries the same scoped operation and reports the failure.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill is the right choice for developers already using oh-my-claudecode who need to exit a stuck or finished autopilot, ralph, swarm or team run. Start with the default command, and only use --force or --all when you understand what state they can discard. If you have not installed oh-my-claudecode, or you want to keep work in progress without risk, this skill is not the right tool.

Download the skill