cancel

Cancel active OMC modes across sessions with forced cleanup.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ClementATH/oh-my-claudecode --skill cancel-clementath
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/ClementATH/oh-my-claudecode/tree/main/skills/cancel
Command: npx skills add https://github.com/ClementATH/oh-my-claudecode --skill cancel-clementath

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancels any active OMC mode (autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team) to ensure a clean shutdown and proper state cleanup.

Core Features & Use Cases

  • Gracefully detects and cancels active modes in session-aware fashion
  • Supports forced global cleanup across all sessions and legacy artifacts
  • Handles team-aware shutdowns with cleanup and optional MCP handling

Quick Start

Tell the system to cancel all active OMC modes and perform state cleanup.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I safely cancel active OMC modes and clean up session state?

To safely cancel active OMC modes, the system identifies active sessions using state_list_active and state_get_status, applies per-session cancellation across autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team, and performs graceful shutdowns with proper state cleanup.

Can I force a global shutdown of all active OMC sessions at once?

You can force a global shutdown of all active OMC sessions by using the --force flag to clear all sessions across autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team modes, including handling legacy artifact cleanup when no sessions remain.

What is the best way to handle graceful team shutdowns during OMC mode cancellation?

The best way to handle graceful team shutdowns during OMC mode cancellation is using the session-aware cancellation logic, which ensures proper cleanup and optional MCP handling while terminating team mode across active sessions.

Does OMC mode cancellation work with legacy state artifacts when no sessions remain?

OMC mode cancellation works with legacy state artifacts by falling back to legacy cleanup routines when no active sessions remain, ensuring proper state cleanup even without session-aware contexts for autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team modes.

Why does my OMC mode cancellation leave active sessions behind?

OMC mode cancellation may leave active sessions behind if the session-aware cancellation process cannot properly identify them via state_list_active and state_get_status; using the --force flag ensures all sessions and legacy artifacts are cleared globally.

When do I need to use the --force flag to cancel OMC modes?

You need to use the --force flag to cancel OMC modes when standard session-aware cancellation fails to clear all active sessions across autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team, requiring a forced global cleanup of all sessions and legacy artifacts.