cancel

Cancel active OMX modes and clean related session state.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/byonk19-svg/rt-scheduler --skill cancel-byonk19-svg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/byonk19-svg/rt-scheduler/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/byonk19-svg/rt-scheduler --skill cancel-byonk19-svg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel all active OMX modes to ensure a safe, clean exit from ongoing automation workflows without leaving partial state behind.

Core Features & Use Cases

  • Detect active OMX modes (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team) and perform appropriate shutdown sequences.
  • Support per-session cancellation via the state contract, plus a global --force cleanup that removes legacy state and resets environments.
  • Handle dependency-aware cleanup (e.g., autopilot cascades cleanup to Ralph and UltraQA), provide a structured cancel report, and preserve resume data where applicable.
  • Include team-mode cleanup via tmux session termination, team state removal, and overlay stripping to ensure complete sanitization.

Quick Start

Issue /cancel to terminate all active OMX modes and clean up related state.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I safely cancel OMX workflows and clean up active modes?

To safely cancel OMX workflows, issue the /cancel command to terminate running modes like autopilot, ralph, or swarm and clean related state. The tool detects active OMX modes and performs the appropriate structured shutdown sequence automatically.

What is the difference between per-session OMX cancellation and a forced global cleanup?

Per-session OMX cancellation terminates workflows and cleans state for the current session only, while a forced global cleanup uses the --force flag to remove all legacy state and reset environments across multiple sessions simultaneously.

How do OMX dependency-aware cleanup sequences handle connected modes like autopilot and Ralph?

Dependency-aware OMX cleanup cascades termination across connected modes, meaning canceling autopilot automatically triggers cleanup for dependent Ralph and UltraQA modes to ensure no partial state remains behind.

Can I terminate OMX team mode and clean up tmux sessions completely?

Yes, OMX team mode cancellation performs complete sanitization by terminating tmux sessions, removing team state, and stripping overlays to ensure no residual processes or configurations remain active.

Does OMX workflow termination preserve resume data for restarting automation later?

Yes, the structured OMX cancel report preserves resume data where applicable during workflow termination. This allows you to safely exit automation workflows without losing the context needed to restart modes later.