cancel

Cancel active execution modes and clean up state in the Pi environment.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/sartoris-digital/pi-superpowers --skill cancel-sartoris-digital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/sartoris-digital/pi-superpowers/tree/main/skills/cancel
Command: npx skills add https://github.com/sartoris-digital/pi-superpowers --skill cancel-sartoris-digital

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a unified way to halt ongoing processes or execution modes within the Pi environment, preventing runaway processes and ensuring a clean slate.

Core Features & Use Cases

  • Graceful Termination: Safely stops active persistence loops like 'ralph' or 'autopilot'.
  • User-Initiated Stop: Responds to explicit user commands like "cancel" or "/cancel".
  • Stuck Process Recovery: Offers a method to terminate modes that have become unresponsive.

Quick Start

Cancel the currently active execution 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 execution mode that is stuck?

To stop an active execution mode that is stuck, the cancel skill detects active processes, writes a cancel signal to the state, and deactivates modes in dependency order to ensure reliable termination.

What is the best way to terminate persistence loops like ralph or autopilot?

The best way to terminate persistence loops like ralph or autopilot is to use graceful termination, which safely stops active execution modes and cleans up associated state within the Pi environment.

Can I clean up state manually after cancelling an execution mode?

You do not need to clean up state manually after cancelling an execution mode, because the cancel skill automatically writes a cancel signal to the state and cleans up associated state during deactivation.

Why does an execution mode become unresponsive and need to be cancelled?

An execution mode may become unresponsive during its persistence loop, requiring the cancel skill to write a cancel signal to the state and deactivate the mode in dependency order for recovery.

Does cancelling an execution mode terminate dependencies in a specific order?

Yes, cancelling an execution mode deactivates modes in dependency order, ensuring that associated state is cleaned up reliably and preventing runaway processes within the Pi environment.