One-click install
npx skills add https://github.com/realsigridjin/oh-my-codex --skill cancel-realsigridjin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/cancel
Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill cancel-realsigridjin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill safely stops active oh-my-codex orchestration modes and cleans up their associated state, preventing runaway workflows, stale sessions, and conflicting execution processes.

Core Features & Use Cases

  • Automatic Mode Detection: Identifies active autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team, and plan consensus sessions.
  • Dependency-Aware Cleanup: Cancels linked modes in the correct order while preserving resumable autopilot progress when appropriate.
  • Force Reset: Clears all active sessions, legacy state files, team artifacts, and MCP worker resources when a complete workspace reset is needed.
  • Use Case: When an orchestration workflow is stuck or no longer needed, use this Skill to stop it gracefully and release its agents and runtime state.

Quick Start

Ask Codex to cancel any active oh-my-codex mode and clean up its associated session state.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I stop a stuck agent orchestration workflow and clean up its session state?

To stop a stuck orchestration workflow, you must cancel the active mode and clean up its associated runtime state. This process performs dependency-ordered cleanup and graceful team shutdown to release agents and remove stale sessions.

What is the safest way to force reset all active orchestration modes in my workspace?

A force reset safely clears all active orchestration sessions, legacy state files, team artifacts, and MCP worker resources. This complete workspace reset prevents conflicting execution processes and removes runaway workflows entirely.

How does dependency-aware cleanup work when canceling linked orchestration sessions?

Dependency-aware cleanup cancels linked orchestration modes in the correct order while preserving resumable autopilot progress when appropriate. It inspects session-aware state to gracefully shut down team workflows without breaking active dependencies.

Can I cancel specific orchestration modes like autopilot, swarm, or pipeline without affecting other active workflows?

Yes, automatic mode detection identifies active autopilot, swarm, pipeline, ultrawork, and team consensus sessions. You can target specific workflows for cancellation while applying dependency-ordered cleanup to preserve unrelated active runtime state.

When should I use a force reset instead of a graceful team shutdown for my orchestration agents?

Use a force reset when you need a complete workspace reset to clear legacy state files and MCP worker artifacts. A graceful team shutdown is preferred when stopping active workflows while preserving resumable progress and valid runtime state.

Why do stale orchestration sessions cause conflicting execution processes and how do I resolve them?

Stale sessions cause conflicting execution processes when orchestration modes remain active without proper runtime state cleanup. Resolve them by canceling the active mode, which triggers session-aware state inspection and removes orphaned team artifacts.