cancel

Cancel active OMC modes and clean up session state.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Hyeonjun0527/yeon --skill cancel-hyeonjun0527
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Hyeonjun0527/yeon/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/Hyeonjun0527/yeon --skill cancel-hyeonjun0527

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel active OMC modes to prevent stale workflows and ensure clean state restoration when work is completed or interrupted.

Core Features & Use Cases

  • Automatically detects the active OMC mode per session and applies dependency-aware cancellation across autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team, and plan consensus; supports force mode to erase all sessions and legacy artifacts.
  • Graceful handling of teams and MCP workers with state cleanup, team shutdown, and orphan cleanup guidance; preserves resume data for autopilot if applicable.
  • Ensures skill-active state is cleared to prevent repeated triggers; operates with session-scoped paths first, then legacy state as fallback.

Quick Start

Invoke the cancel command to stop all active OMC modes and remove related state.

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 OMC mode and clean up session state?

Cancel an active OMC mode by invoking the cancel command, which applies dependency-aware cancellation across sessions and clears related state to prevent stale workflows from persisting across restarts. It safely shuts down modes like autopilot, ultrawork, and pipeline.

What is the best way to perform a graceful shutdown of OMC swarm and team workflows?

For a graceful shutdown of OMC swarm and team workflows, the cancel command handles state cleanup, team shutdown, and orphan cleanup guidance. It preserves resume data for autopilot if applicable while ensuring skill-active state is cleared.

How do I force cleanup of all OMC sessions and legacy artifacts?

Force cleanup of all OMC sessions and legacy artifacts by running the cancel command with the --force flag. This enables global cleanup, erasing all active modes and legacy state artifacts that standard session-scoped cancellation might leave behind.

Which OMC modes are supported for dependency-aware session cancellation?

Dependency-aware session cancellation supports OMC modes tracked by the session-aware state contract, including autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, team, plan consensus, and self-improve.

Do I need specific state management tools to cancel OMC modes?

Yes, canceling OMC modes requires access to specific state management tools including state_list_active, state_get_status, state_clear, and state_write. These tools enable the dependency-aware cancellation order needed for safe shutdown.

Why does an OMC workflow persist across restarts and how do I stop it?

An OMC workflow persists across restarts because stale session state remains active. Stop it by running the cancel command, which clears the skill-active state and removes related session data, operating with session-scoped paths first and legacy state as fallback.