cancel

Cancel active OMX modes with dependency-aware session cleanup.

1|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/prthik/prathik-astro --skill cancel-prthik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/prthik/prathik-astro/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/prthik/prathik-astro --skill cancel-prthik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Cancel Skill detects and cancels the active OMX mode across all supported modes, providing a safe, consistent exit path and preserving work state where applicable.

Core Features & Use Cases

  • Detects the active mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team) and cancels it.
  • Supports per-session cancellation or a force-wide cleanup of legacy state, with dependency-aware ordering.
  • Handles team-based cleanup via tmux and .omx state scavenging, including structured cancel reports.

Quick Start

Run /cancel to terminate the active OMX mode and perform proper 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 my current session state?

To cancel an OMX mode safely, run a session-scoped cancellation with a provided session_id, which terminates the active mode using dependency-aware ordering while preserving resume data and generating a structured cancel report.

What is the proper way to clean up legacy OMX state across all sessions?

Cleaning up legacy OMX state requires executing a force-wide cancellation using the --force and --all options, which clears all active sessions and legacy state while maintaining dependency-aware cancellation ordering and preserving resume data.

How does dependency-aware cancellation work when exiting OMX modes like autopilot or swarm?

Dependency-aware cancellation works by identifying the active mode—such as autopilot, swarm, or pipeline—and terminating it following a defined order, ensuring that interconnected processes are safely stopped without breaking the overall session state.

Can I use tmux to perform team-based cleanup for OMX sessions?

Yes, team-based cleanup is handled by scavenging tmux and .omx state files, allowing you to identify and cancel active modes across team environments while generating a structured cancel report for the cleared sessions.

When should I use a force-wide cleanup instead of a standard session cancel?

Use a force-wide cleanup when you need to clear all active sessions and legacy state simultaneously, whereas a standard session cancel targets only the active mode within a single specified session_id.