cancel

Cancel active OMX modes and clean up session state.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/eszxcvfd/ANIZAKI --skill cancel-eszxcvfd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/eszxcvfd/ANIZAKI/tree/main/.agents/skills/cancel
Command: npx skills add https://github.com/eszxcvfd/ANIZAKI --skill cancel-eszxcvfd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel active OMX modes and perform safe state cleanup to avoid lingering processes or inconsistent state.

Core Features & Use Cases

  • Automatic detection of the active mode (Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, Team) and coordinated shutdown.
  • Supports forceful cleanup across all sessions with --force/--all and preserves safe defaults for session-scoped cancellation.
  • Handles special cases like linked Ralph or team workflows and cleans up related state artifacts.

Quick Start

Run the /cancel command to terminate the current OMX session and purge 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 an active OMX mode and clean up state?

Running the /cancel command safely stops active OMX modes like Autopilot, Ralph, or Ultrawork and performs state cleanup to remove lingering processes and inconsistent session data.

What happens to linked Ralph or team workflows when I stop OMX modes?

Linked Ralph or team workflows are safely stopped through session-aware cancellation that coordinates shutdown across linked sessions and cleans up related state artifacts.

Can I forcefully stop all OMX modes across multiple sessions?

Yes, you can forcefully stop all OMX modes across multiple sessions using the --force or --all flags, which perform global cleanup of tmux sessions and legacy artifacts.

Does the OMX cancellation process support tmux session management?

Yes, the OMX cancellation process supports tmux session management by handling tmux session cleanup and removing legacy artifacts during both session-scoped and global cancellation.

Why is safe state cleanup necessary after terminating OMX modes?

Safe state cleanup is necessary after terminating OMX modes to avoid lingering processes or inconsistent state that can result from incomplete session shutdowns or linked-mode workflow cancellations.

When should I use global cleanup instead of session-scoped cancellation?

You should use global cleanup with --force or --all instead of session-scoped cancellation when multiple OMX modes are running across different sessions and you need to purge legacy artifacts comprehensively.