cancel

Detects and cancels active OMX modes with session-aware state cleanup.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill cancel-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill cancel-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When running OMX workflow modes like autopilot, ralph, ultrawork, or team, stale state files and orphaned tmux sessions can linger after work completes. This Skill provides a single, safe way to detect which mode is active and shut it down cleanly, preserving resumable progress where supported. ## Core Features & Use Cases - Auto-Detection of Active Modes: Inspects session-scoped state via state_list_active and state_get_status to identify which of the ten OMX modes (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team, plan consensus) is running. - Dependency-Ordered Cancellation: Cancels modes in a defined order, cleaning up linked modes (e.g., ralph's linked ultrawork) while leaving unrelated sessions untouched. - Graceful Team Shutdown: Sends shutdown inboxes to tmux-based team workers, waits for graceful exit, then force-kills unresponsive panes and destroys the tmux session. - Force Reset: The --force or --all flag clears every session plus legacy state files under .omx/state/ for a full workspace reset. - Use Case: After an autopilot run finishes, invoke the cancel skill to mark it inactive while preserving phase, plan, and verdict state so you can resume later with /autopilot. ## Quick Start Ask the AI to cancel the currently active OMX mode, or add the force flag to clear all sessions and legacy state files.

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 autopilot or ralph session?

Invoke the cancel skill with no arguments. It auto-detects the active mode via state tools and cancels it in dependency order, cleaning up linked modes like ralph's linked ultrawork while preserving autopilot state for resume.

How do I reset all OMX state files at once?

Run the cancel skill with the --force or --all flag. It iterates every session with state_clear, then removes legacy files under .omx/state/*.json, swarm databases, and team artifacts for a complete workspace reset.

Does cancelling autopilot delete my progress?

No. Autopilot cancellation marks the state inactive but preserves phase, files, spec, plan, and verdicts. You can resume later by running /autopilot again.

What happens to tmux team workers when I cancel team mode?

The skill writes a shutdown inbox to each worker, waits up to 15 seconds for graceful exit, then force-kills unresponsive panes and destroys the omx-team-* tmux session. Team state directories and the AGENTS.md overlay are also removed.

Why does cancel refuse to stop ultrawork linked to ralph?

Standalone ultrawork cancellation checks the linked_to_ralph flag and exits with an error if set. Cancelling the parent ralph mode automatically cleans up its linked ultrawork or ecomode state in the same scope.