cancel

Cancel active OMX modes and clean up session state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel any active OMX mode (autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, team) to safely terminate ongoing workflows and clean up related state.

Core Features & Use Cases

  • Detects an active OMX mode and cancels it across Autopilot, Ralph, Ultrawork, UltraQA, Swarm, Ultrapilot, Pipeline, and Team.
  • Handles session-scoped cleanup via state tools or legacy files, with dependency-aware cancellation order.
  • Supports --force / --all for global cleanup and forcefully terminates teams when needed.

Quick Start

Run the /cancel command to gracefully terminate all active OMX modes and perform full state cleanup.

Frequently Asked Questions about cancel

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

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

To safely cancel OMX automation workflows and clean up state, run the cancel command to gracefully terminate active modes and execute per-session state sanitization across all running processes.

What OMX modes are supported for state cleanup and termination?

Supported OMX modes for state cleanup include autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team, enabling comprehensive termination of any active automation workflow.

How do I force terminate all active OMX modes across multiple sessions?

Force terminating all active OMX modes across multiple sessions requires using the --force and --all flags during cancellation to execute global cleanup and forcefully terminate running teams.

Can I clean up OMX state using legacy files instead of session-aware tools?

Yes, you can clean up OMX state using legacy files as a fallback, since the cancellation logic handles both session-scoped cleanup via state tools and legacy file-based state management.

What is the cancellation order when terminating OMX team workflows?

The cancellation order for OMX team workflows is dependency-aware, ensuring safety controls are applied during per-session cleanup and global sanitization to prevent orphaned processes or corrupt state.