cancel

Detect and shut down active oh-my-codex modes with cleanup routines.

20|6|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/sigridjineth/oh-my-codex --skill cancel-sigridjineth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/sigridjineth/oh-my-codex/tree/main/skills/cancel
Command: npx skills add https://github.com/sigridjineth/oh-my-codex --skill cancel-sigridjineth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a unified and intelligent way to stop and clean up any currently running "oh-my-codex" (OMC) operational mode, preventing resource waste and ensuring a clean slate.

Core Features & Use Cases

  • Mode Detection: Automatically identifies the active OMC mode (e.g., Autopilot, Ralph, Team, Swarm).
  • Graceful Shutdown: Initiates a controlled shutdown sequence tailored to the specific mode, respecting dependencies and linked processes.
  • Force Cleanup: Offers an option to forcefully clear all active sessions and legacy artifacts for a complete reset.
  • Use Case: You've started a long-running "autopilot" task but need to stop it immediately to address an urgent issue. Running /oh-my-codex:cancel will safely halt the autopilot, preserving your progress for later resumption, and cleaning up any associated Ralph or UltraQA processes.

Quick Start

Safely stop the currently active oh-my-codex mode.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I stop an active oh-my-codex workflow without losing my progress?

To stop an active oh-my-codex workflow, you can initiate a graceful shutdown that detects the running process and executes mode-specific cleanup routines. This safely halts tasks while preserving your progress for later resumption.

What is the best way to cancel complex multi-agent tasks like Autopilot or Swarm?

The best way to cancel multi-agent tasks like Autopilot or Swarm is to use a unified cancellation command that targets the specific mode. It handles dependencies between linked processes to ensure a controlled and complete termination.

How does cleanup work for linked processes when stopping an OMC Autopilot task?

Cleanup for linked processes works by respecting dependencies during the shutdown sequence. When stopping an Autopilot task, the system automatically cleans up any associated Ralph or UltraQA processes to prevent resource waste.

Can I forcefully clear all active OMC sessions and legacy artifacts for a full reset?

Yes, you can forcefully clear all active oh-my-codex sessions and legacy artifacts. This force cleanup option bypasses graceful shutdowns to execute a system-wide state clearing, ensuring a completely clean slate.

Does canceling an OMC mode require manually identifying the active process?

No, canceling an OMC mode does not require manual process identification. The system features automatic mode detection that identifies the active operational mode and applies the appropriate mode-specific cleanup routines.

Why should I use a dedicated cancellation routine instead of manually killing agent processes?

Using a dedicated cancellation routine prevents resource waste and state corruption by handling complex dependencies between modes. Manually killing processes may leave behind active sessions and legacy artifacts that disrupt future workflows.