cancel

Cancels active OMX workflows and removes their session state in Sprite Harness.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/hotaq/Sprite_harmess --skill cancel-hotaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/hotaq/Sprite_harmess/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/hotaq/Sprite_harmess --skill cancel-hotaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill stops active OMX modes cleanly when work is complete, preventing orphaned state, stale workers, and inconsistent session data.

Core Features & Use Cases

  • Mode-aware cancellation: Detects and cancels active workflows such as autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team, and plan consensus.
  • Safety-first cleanup: Handles linked state carefully, preserves resumable autopilot progress when appropriate, and avoids mutating unrelated sessions.
  • Operational recovery: Supports force cleanup for stale or legacy artifacts, plus team shutdown flows that coordinate tmux workers and workspace state.
  • Use case: When a development session finishes or gets stuck, use this Skill to shut it down without leaving behind broken locks, partial state, or dangling worker processes.

Quick Start

Ask the cancel skill to stop the currently active OMX mode and clean up its session state safely.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I safely cancel active OMX workflows and clean up session state?

To safely cancel OMX workflows, use a session-aware shutdown process that detects active modes and performs dependency-ordered cleanup. This removes associated session state and prevents orphaned workers or broken locks.

What happens to tmux workers and linked state when stopping autopilot or swarm workflows?

Stopping autopilot or swarm workflows handles linked state carefully and coordinates tmux worker shutdown. It preserves resumable progress when appropriate while safely removing dangling worker processes.

Can I force remove stale OMX artifacts and legacy session state from a local Sprite Harness?

Yes, you can force remove stale artifacts and legacy session state in local Sprite Harness environments. Force mode overrides standard safety checks to clear broken locks and inconsistent data.

Which OMX modes are supported for workflow shutdown and session cleanup?

Supported OMX modes for workflow shutdown include autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team, and plan consensus. Each mode undergoes session-aware detection for safe removal.

Why does my development session leave orphaned state and broken locks after finishing?

Orphaned state and broken locks occur when workflows finish without dependency-ordered cleanup. Properly shutting down the session ensures linked-state handling and safe removal of all associated artifacts.

Do I need a local Sprite Harness environment to shut down team consensus workflows?

Yes, canceling team and plan consensus workflows requires a local Sprite Harness environment. The cleanup process relies on session-aware detection within this specific infrastructure to coordinate workspace state.