cancel

Cancel active OMC modes by clearing local .omc/state files.

38.5k|3.5k|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill cancel-yeachan-heo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/cancel
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill cancel-yeachan-heo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a safe, centralized way to cancel any active OMC mode by detecting and cleaning up local state, ensuring a clean transition back to idle.

Core Features & Use Cases

  • Detects active modes (Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, Plan Consensus) and performs appropriate cleanup.
  • Supports a forceful reset (--force / --all) to remove all OMC state and stop related daemons, enabling a fresh start.
  • Handles team-based cancellations with graceful shutdown, audit reporting, and local state cleanup.

Quick Start

Run /oh-my-claudecode:cancel to terminate all active OMC modes. To force a complete reset, use: /oh-my-claudecode:cancel --force

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel active OMC modes like Autopilot or Swarm?

To cancel active OMC modes, run the cancel command to clear local state files in .omc/state. It detects modes like Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, and Plan Consensus, performing safe state cleanup and reporting results.

How do I force stop all running OMC daemons and reset state?

Use the force reset option by running cancel with --force or --all. This forcefully removes all OMC state files, stops related daemons, and resets the environment back to a clean idle state for a fresh start.

Can I handle team-based cancellation for OMC modes?

Yes, cancel supports team-based cancellations with graceful shutdown, audit reporting, and local state cleanup. It inspects .omc/state files to determine activity and performs safe cleanup for team-aware mode termination.

What is the safest way to clean up local OMC state files?

The safest way to clean up local OMC state files is to run the cancel command without force flags. It inspects .omc/state to detect active modes and performs appropriate cleanup using standard shell utilities, reporting results without forcefully stopping daemons.

Does cancel require any external dependencies to stop OMC modes?

No, cancel relies solely on standard shell utilities and requires no external dependencies. It inspects .omc/state files directly to determine active modes and perform safe state cleanup and reporting.

When should I use a forceful reset instead of a standard OMC cancellation?

Use a forceful reset when standard cleanup fails or when you need to remove all OMC state and stop related daemons completely. If a mode is stuck or unresponsive, --force ensures a complete reset back to idle.