cancel

Cancel active OMX modes and clean up session-scoped workspace state.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill cancel-kyrie66nb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/cancel
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill cancel-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel active OMX modes and perform proper state cleanup to ensure a clean slate for resume or switching modes.

Core Features & Use Cases

  • Detects the active OMX mode and cancels it, performing necessary cleanup to preserve resume state where applicable.
  • Supports a robust, dependency-aware workflow (Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, Team) with safe fallbacks.
  • Provides a graceful and forced cancellation path via --force/--all, including team tmux-based shutdown.

Quick Start

Cancel the active OMX mode to reset the workspace.

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 OMX modes and clean up workspace state?

You can cancel team modes and shut down associated tmux sessions using the --force flag, which triggers a safe, thorough tmux-based shutdown to ensure complete state cleanup across the team workflow.

What OMX workflow modes can be cancelled and reset?

Global cleanup across all active OMX modes is supported via the --all flag, which forces cancellation and resets the workspace state globally, bypassing standard graceful shutdown paths for a complete reset.

Why does OMX state cleanup preserve resume state during cancellation?

State cleanup preserves resume state because the graceful cancellation path detects the active OMX mode and performs necessary cleanup specifically designed to maintain a clean slate for resuming or switching modes without losing session-scoped workflow data.

Do I need any dependencies installed to cancel OMX workflows?

No dependencies are required to cancel OMX workflows, as the Skill operates independently to detect active modes and perform state cleanup, although team mode tmux shutdown relies on the existing tmux session environment.