cancel

Cancel active Forge modes and execute mode-specific cleanup commands.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Users need a reliable way to abort ongoing Forge modes without leaving residual state or requiring manual cleanup.

Core Features & Use Cases

  • Auto‑detection of the currently active Forge mode across sessions.
  • Mode‑specific cancellation for autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team.
  • Forceful cleanup with --force or --all flags to erase all session and legacy artifacts.
  • Safe shutdown that preserves necessary state for resumable modes (e.g., autopilot) while ensuring no unrelated sessions are affected.

Quick Start

Ask the assistant to execute /cancel to terminate the current Forge mode.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I stop an active Forge workflow session?

To stop an active Forge workflow, execute the /cancel command to auto-detect the running mode and trigger mode-specific cleanup commands. This instantly halts the ongoing session without requiring manual intervention.

What is the best way to abort autopilot or ultrawork modes in Forge?

The best way to abort autopilot or ultrawork modes is using a command that detects the active session state and applies mode-specific cancellation. Safe shutdown preserves necessary state for resumable modes while ensuring unrelated sessions remain unaffected.

Can I forcefully remove all legacy session artifacts when canceling a Forge mode?

Yes, you can forcefully remove all legacy session artifacts by applying the --force or --all flags during cancellation. This ensures full state removal and erases any residual data left behind by the aborted workflow.

Does Forge cancellation work across different automation modes like ralph, swarm, and pipeline?

Yes, Forge cancellation works across multiple automation modes including ralph, swarm, pipeline, ultraqa, ultrapilot, ecomode, and team. It requires detecting the active session state to execute the correct mode-specific cleanup commands.

Why does my Forge session leave residual state after manual termination?

Manual termination often leaves residual state because it bypasses mode-specific cleanup commands. Using an automated cancellation process ensures safe shutdown and proper state preservation or removal, preventing leftover legacy artifacts from accumulating.