cancel

Cancel active OMC modes and clean session state artifacts.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/oneforce/oh-my-gemini-cli --skill cancel-oneforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/oneforce/oh-my-gemini-cli/tree/main/skills/cancel
Command: npx skills add https://github.com/oneforce/oh-my-gemini-cli --skill cancel-oneforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canceling an active OMC session can be error-prone and leave modes partially running or with stale state. This skill provides a safe, centralized way to terminate any active OMC mode and perform proper cleanup so you can start fresh.

Core Features & Use Cases

  • Detects which OMC mode is active across sessions and cancels in dependency order (Autopilot → Ralph → Ultrawork → UltraQA → Swarm → Ultrapilot → Pipeline → Team).
  • Supports per-session cancellation by default and a force-wide cleanup that clears legacy state artifacts.
  • Handles Gemini Code native teams, performs TeamDelete, and clears linked artifacts (ralph, ultrawork) as needed to maintain a consistent workspace.

Quick Start

Invoke the cancel command to terminate the currently active OMC mode, for example: /oh-my-gemini-cli:cancel or say 'cancelomg'.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I gracefully cancel an active OMC mode and clean up stale session state?

To cancel an active OMC mode, invoke a centralized shutdown command that detects running sessions and terminates them in dependency order to ensure a clean, resumable workspace without stale artifacts.

What is the safest way to terminate multiple running OMC sessions across a workspace?

Terminating multiple OMC sessions safely involves using a force-wide cleanup feature that detects active modes across all known sessions and removes legacy state artifacts for a consistent workspace.

How do I shut down an OMC autopilot or team mode without leaving partial processes running?

Shutting down OMC autopilot or team modes requires a dependency-aware shutdown process that cancels active modes in a specific sequence, preventing partial runs and clearing linked artifacts.

Can I cancel a specific OMC session instead of forcing a workspace-wide shutdown?

Yes, you can cancel a specific OMC session instead of a workspace-wide shutdown, as the cancellation tool supports per-session termination by default while detecting active modes through session-aware state tools.

Why does canceling an OMC mode manually leave legacy state artifacts behind?

Manual cancellation often leaves legacy state artifacts because it lacks dependency-aware shutdown logic, whereas using an automated cancellation skill purges related team and MCP artifacts for a consistent workspace.