cancel

Cancel active OMX modes and terminate related tmux sessions.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/zchee/json-repair-rs --skill cancel-zchee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/zchee/json-repair-rs/tree/main/.codex/skills/cancel
Command: npx skills add https://github.com/zchee/json-repair-rs --skill cancel-zchee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill swiftly terminates any active OMX modes, preventing conflicts and ensuring a clean state for new operations.

Core Features & Use Cases

  • Mode Cancellation: Detects and cancels active modes such as autopilot, Ralph, ultrawork, and others automatically.
  • Session & Team Management: Handles tmux team sessions by gracefully shutting down worker processes and cleaning up related state files.
  • Use Case: When multiple AI sessions are running concurrently and need resetting, use this Skill to cancel all active modes and terminate relevant processes efficiently.

Quick Start

Say "cancel" to terminate all active OMX modes and clean up associated state.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cancel active OMX modes like autopilot or ultrawork?

To cancel active OMX modes like autopilot or ultrawork, you can use a command to automatically detect and terminate ongoing workflows. This ensures a clean environment by performing graceful shutdowns or force kills when necessary.

What is the best way to reset tmux team sessions before starting a new task?

The best way to reset tmux team sessions is to gracefully shut down worker processes and clean up related state files. This workflow reset prevents conflicts from concurrent AI sessions and prepares the workspace for new operations.

How do I clean up state directories after an AI session failure?

To clean up state directories after an AI session failure, you need to cancel ongoing modes and force kill relevant processes. This state cleanup removes leftover files from failed workflows and restores a clean baseline for new tasks.

When should I use a force kill to terminate concurrent AI workflows?

You should use a force kill to terminate concurrent AI workflows when graceful shutdowns fail to stop active modes. This ensures stubborn processes in tmux sessions and state directories are fully terminated for a complete workspace reset.