cancel

Cancel active OMX modes and clean up session state.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HaydernCenterpoint/oh-my-qwen --skill cancel-hayderncenterpoint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/HaydernCenterpoint/oh-my-qwen/tree/main/skills/cancel
Command: npx skills add https://github.com/HaydernCenterpoint/oh-my-qwen --skill cancel-hayderncenterpoint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canceling an active OMX mode to restore normal operation and preserve state where appropriate.

Core Features & Use Cases

  • Auto-detects which OMX mode is active (Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, Team) and terminates it with appropriate cleanup.
  • Supports forceful fallback with --force or --all to clear all sessions and legacy state artifacts when needed.
  • Handles team-based cancellations with tmux-based workers, grace period, and cleanup of team state.

Quick Start

Tell the system to cancel the current OMX session to stop all active modes.

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 and clean up its session state?

To cancel an active OMX mode, the system auto-detects the running mode and terminates it using state utilities like state_clear, ensuring safe and resume-friendly cleanup per session.

How do I forcefully clear all OMX sessions and legacy state files across my workspace?

You can forcefully clear all OMX sessions and legacy state artifacts across the workspace by using the --force or --all flag, bypassing the default per-session cancellation behavior.

How does canceling a team-based OMX mode handle tmux workers and grace periods?

Canceling a team-based OMX mode terminates tmux-based workers, enforces a grace period for safe shutdown, and executes targeted cleanup of the associated team state files.

What OMX modes can be safely terminated with resume-friendly state cleanup?

The system safely terminates Autopilot, Ralph, Ultrawork, Ecomode, UltraQA, Swarm, Ultrapilot, Pipeline, and Team modes, applying mode-specific cleanup routines to preserve resume-friendly state.

Do I need specific state management dependencies to cancel an OMX session?

No external dependencies are required, as the cancellation process internally relies on built-in state utilities including state_list_active, state_get_status, and state_clear to manage session cleanup.

Why is my OMX session not restoring normal operation after a standard cancel?

If standard per-session cancel fails to restore operation, legacy state artifacts may persist; using the forceful fallback with --force clears all sessions and legacy files to resolve it.