cancel

Cancel active OMX modes and clean up related state across sessions.

1|Updated Mar 15, 2026

Search Tags:#workflow #tmux #state-management #cancel #omx #team-cleanup

Ready to run

npx skills add https://github.com/Linnanli/xClaw --skill cancel-linnanli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Linnanli/xClaw/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/Linnanli/xClaw --skill cancel-linnanli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel active OMX modes and perform state cleanup to gracefully shut down workflows and prevent orphaned processes or inconsistent state.

Core Features & Use Cases

Graceful and forceful cancellation across multiple OMX modes (Autopilot, Ralph, Ultrawork, UltraQA, Swarm, Ultrapilot, Pipeline, Team).
Session-aware cleanup using state tools (state_list_active, state_get_status) with per-session scope, plus optional legacy cleanup with --force/--all.
Team-based shutdown handling via tmux integration, worker inbox signaling, and comprehensive state cleanup, with structured cancellation reports.
Dependency-aware sequencing and safe cleanup, preserving progress where applicable (Autopilot) and ensuring unsafe actions are avoided when possible.

Quick Start

Use the cancel skill to terminate all active OMX modes and clean up their state.

Frequently Asked Questions about cancel

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

FAQPage Schema

How do I gracefully stop OMX workflows and clean up their state?▼

To stop OMX workflows, use cancellation logic that targets active OMX modes and performs session-aware state cleanup. It applies graceful termination across modes like Autopilot and Ralph, using state_list_active and state_get_status to safely clear the workspace and prevent orphaned processes.

How do I force cancel active OMX modes and clear legacy state?▼

Force canceling active OMX modes uses the --force flag to ensure immediate termination, while the --all flag triggers comprehensive legacy-state cleanup via state_clear. This handles both per-session scope and legacy data for a fully reset workspace.

What is the best way to handle team-based workflow shutdown in tmux?▼

The best way to handle team-based workflow shutdown in tmux is using structured cancellation that integrates with tmux, signals worker inboxes, and performs comprehensive state cleanup. This ensures all team workers are safely terminated without leaving inconsistent state.

Does OMX state cleanup preserve workflow progress when stopping Autopilot?▼

Yes, OMX state cleanup preserves workflow progress where applicable when stopping Autopilot. The cancellation logic uses dependency-aware sequencing and safe cleanup to avoid unsafe actions, ensuring progress is retained during both graceful and forceful termination.

Why are orphaned processes left behind after terminating OMX modes?▼

Orphaned processes are left behind when terminating OMX modes if state cleanup is incomplete. Session-aware cancellation resolves this by using state_list_active to identify active sessions and state_clear to remove legacy state, ensuring no orphaned processes remain.