cancel

Cancel active OMC modes and clear session and legacy state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill stops runaway or stuck OMC modes and cleans up session and legacy state so agents, teams, and workflows do not continue consuming resources or leave inconsistent state behind while preserving autopilot resume data when appropriate.

Core Features & Use Cases

  • Automatic detection: Inspects session-aware state and legacy artifacts to determine which OMC mode(s) are active.
  • Mode-aware cancellation: Cancels autopilot, ralph, ultrawork, ultraqa, swarm, ultrapilot, pipeline, and team workflows in dependency order and preserves autopilot state for resume.
  • Force and fallback: Supports --force/--all to remove legacy artifacts and includes a documented bash fallback to remove state files when deferred tools are unavailable.
  • Team-safe shutdown and orphan cleanup: Performs graceful teammate shutdown, TeamDelete, and process orphan scanning/killing for tmux and worker daemons.
  • Use cases include terminating stuck multi-agent runs, resetting workspace state before fresh runs, and recovering resources from orphaned team processes.

Quick Start

Invoke the cancel skill by running /oh-my-claudecode:cancel --force to stop active modes and clean session state.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel a stuck OMC autopilot or team workflow?

To cancel a stuck OMC workflow, invoke the cancel skill with --force to stop active modes like autopilot or team in dependency order, clear their session state, and perform graceful teammate shutdown.

What is the best way to clean up legacy OMC state files before a fresh run?

Cleaning up legacy OMC state files requires the cancel skill's --all flag to remove artifacts, or its documented bash fallback path to manually remove state files when deferred tools are unavailable.

Does canceling OMC workflows delete autopilot resume data?

Canceling OMC workflows does not delete autopilot resume data; the cancel skill performs mode-aware cancellation that preserves autopilot state while clearing session and legacy state for other active modes.

How do I kill orphaned tmux or worker daemon processes left by OMC team runs?

To kill orphaned tmux or worker daemon processes left by OMC team runs, use the cancel skill to perform process orphan scanning and killing, followed by TeamDelete to ensure complete resource recovery.

What session-aware state tools are required to reset OMC workspace state?

Resetting OMC workspace state requires session-aware state tools including state_list_active, state_get_status, state_clear, state_read, and state_write, with optional TeamDelete and ToolSearch support for complete cleanup.