cancel

Cancel active OMB modes with graceful shutdown and state cleanup.

3|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Tienching/oh-my-codebuddy --skill cancel-tienching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/Tienching/oh-my-codebuddy/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/Tienching/oh-my-codebuddy --skill cancel-tienching

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancels any active OMB mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team) safely and consistently, ensuring state is preserved where needed and cleanup is performed to prevent stuck workflows.

Core Features & Use Cases

  • Detects active sessions and modes using the official state tools (state_list_active, state_get_status) to determine which OMB mode is running.
  • Performs a two-pass cancellation: graceful shutdown of active workers or components, followed by a forceful cleanup if required (--force/--all).
  • Handles both standalone modes and team-based workflows (tmux-based teams) with proper state cleanup and reporting.

Quick Start

Identify any active OMB modes and cancel them safely.

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 OMB workflow safely?

Cancel active OMB workflows safely by initiating a two-pass shutdown that gracefully terminates workers while preserving state, followed by a forceful cleanup using the --force flag if required.

What is the best way to stop stuck tmux-based team sessions?

Stop stuck tmux-based team sessions by detecting active modes with state_list_active, performing graceful worker termination, and executing proper state cleanup and reporting to ensure no processes remain hanging.

Does the OMB cancellation process support per-session scoping?

Yes, OMB cancellation supports per-session scoping, allowing you to target specific active workflows rather than terminating all modes, while utilizing state_get_status to verify the current running context.

How do I force cleanup across all active OMB modes at once?

Force cleanup across all active OMB modes simultaneously by applying the --all flag, which overrides graceful shutdowns and executes immediate state_clear operations to remove stuck workflows across autopilot, swarm, and ultrapilot modes.

Why does my OMB workflow state remain active after cancellation?

OMB workflow state remains active after cancellation when the graceful shutdown fails to terminate workers, requiring a forceful cleanup pass with --force to properly execute state_clear and remove the residual status.

Can I cancel workflows across different OMB modes like ultrawork and ultraqa?

Yes, you can cancel workflows across ultrawork, ultraqa, pipeline, and other OMB modes, as the process detects the specific active mode using official state tools and applies the appropriate termination and cleanup logic.