cancel

Cancel active OMX modes and emit a structured cancel report.

Updated Jan 4, 2026

Search Tags:#cleanup #session #team #state #shutdown #cancel #omx

Ready to run

npx skills add https://github.com/YeaChan05/Remittance --skill cancel-yeachan05

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/YeaChan05/Remittance --skill cancel-yeachan05

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancels any active OMX mode across the system, ensuring proper cleanup and readiness for a safe resume later.

Core Features & Use Cases

Detects the currently active OMX mode (Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, Team) and terminates it gracefully, preserving progress where applicable.
Supports per-session cancellation or a global force cleanup across all sessions, with a safe fallback to clear legacy state.
Handles team-based cancellations via tmux-based workers, including cleanup of team state and artifacts, and provides a structured cancel report.

Quick Start

Invoke /cancel to terminate the active OMX mode in the current session and perform safe cleanup.

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 OMX mode safely without losing Autopilot progress?▼

To cancel an OMX mode safely, invoke the cancel command to terminate the active session gracefully. It performs mode-specific cleanup while preserving Autopilot progress, ensuring the system is ready for a safe resume later.

What is the best way to force cleanup OMX session and team state across all sessions?▼

The best way to force cleanup OMX state globally is to use the cancel command with the --force or --all flag. This clears all active sessions and team modes, removing legacy state and artifacts while emitting a structured report.

How does OMX mode cancellation handle team-based tmux workers?▼

OMX mode cancellation handles team-based tmux workers by terminating the active mode gracefully and cleaning up team state and associated artifacts. It performs mode-specific cleanup across the tmux sessions and emits a structured cancel report.

When do I need to perform an OMX session shutdown?▼

You need to perform an OMX session shutdown when an active mode like Autopilot, Ralph, Ultrawork, UltraQA, Swarm, or Pipeline is running and requires graceful termination. Canceling ensures proper cleanup and safe readiness for later resumption.

Can I remove legacy OMX state without affecting my current session?▼

Yes, you can remove legacy OMX state safely. The cancel command operates per session by default and includes a safe fallback to clear legacy state when appropriate, performing mode-specific cleanup without disrupting other active sessions.