cancel

Cancel active Claude on Web execution modes by detecting and removing .omc/state artifacts.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/ssccio/cc-on-web-base --skill cancel-ssccio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/ssccio/cc-on-web-base/tree/main/skills/cancel
Command: npx skills add https://github.com/ssccio/cc-on-web-base --skill cancel-ssccio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of getting stuck in an active Claude on Web (OMC) execution mode when you need to stop quickly and cleanly.

Core Features & Use Cases

  • Auto-detects the active OMC mode by checking mode-specific state files and markers across autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and plan consensus.
  • Performs dependency-aware cancellation so higher-level modes clean up linked lower-level modes in the correct order.
  • Preserves safe resumability for Autopilot by marking it inactive while keeping its state so you can continue later.
  • Supports a force clear option that removes all relevant local .omc/state/ artifacts regardless of what is detected.

Example: You started an autopilot run that spawned ralph/ultraqa work and it’s no longer needed—use cancel to stop everything and ensure the system returns to a clean idle state.

Quick Start

Run /oh-my-claudecode:cancel to cancel the currently active OMC mode with dependency-aware cleanup.

Frequently Asked Questions about cancel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I cancel an active Claude Code OMC mode and clean up state files?

Canceling an active OMC execution mode stops workflows like autopilot or ralph by detecting state files in .omc/state and deactivating them. It performs dependency-aware cleanup to ensure higher-level modes and their linked lower-level modes stop in the correct order.

How does dependency-aware mode cancellation work for linked OMC workflows?

Dependency-aware cancellation identifies linked OMC workflows and deactivates higher-level modes before cleaning up lower-level modes. This priority-based cancellation order ensures that complex linked scenarios like an autopilot run spawning ultraqa work are stopped cleanly without orphaned processes.

Can I force clear all OMC state artifacts without detecting the active mode?

Yes, you can force clear all OMC state artifacts by passing the --force or --all argument. This removes every relevant file in the local .omc/state/ directory regardless of which specific execution mode is currently detected as active.

Does canceling autopilot mode delete the state file or preserve it for resuming?

Canceling autopilot mode preserves safe resumability by marking the mode as inactive while keeping its state file intact. This allows you to continue the autopilot run later without losing your previous workflow progress.

What OMC execution modes are supported for workflow cancellation?

Workflow cancellation supports autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and plan-consensus execution modes. The command detects mode-specific markers across these scenarios to apply the correct state file updates.

Do I need jq or sqlite3 to safely update OMC state during cancellation?

You need jq and optionally sqlite3 to safely update or remove OMC state during cancellation. These tools are used to parse arguments and check state artifacts, ensuring the mode-specific files in .omc/state are modified safely.