cancel

Cancel active PEP modes and clean up related session state.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/leejaedus/pepcode --skill cancel-leejaedus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cancel
Source: https://github.com/leejaedus/pepcode/tree/main/skills/cancel
Command: npx skills add https://github.com/leejaedus/pepcode --skill cancel-leejaedus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cancel active PEP modes and clean up related state.

Core Features & Use Cases

  • Graceful and forceful cancellation across autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team
  • Dependency-aware cleanup that preserves resume state for autopilot
  • Session-based and legacy-cleanup pathways with safe fallback

Quick Start

Cancel the active PEP mode for the current session.

Frequently Asked Questions about cancel

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

FAQPage Schema
How do I cleanly cancel an active PEP mode and clean up session state?▼

To cancel an active PEP mode, the tool detects the current mode via state tools and performs per-session cleanup, removing related state artifacts for modes like autopilot, ultrawork, or swarm.

What is the difference between graceful and forceful cancellation for PEP modes?▼

Graceful cancellation performs per-session cleanup while preserving resume state for autopilot, whereas forceful cancellation triggers global cleanup that also removes legacy artifacts across all sessions.

Which PEP modes can I cancel using this state-management approach?▼

You can cancel active modes across autopilot, ralph, ultrawork, ecomode, ultraqa, swarm, ultrapilot, pipeline, and team, detecting the active one through a session-aware state model.

How do I remove legacy artifacts left behind by previous PEP mode sessions?▼

You remove legacy artifacts by using the optional force flag, which triggers a global cleanup pathway that goes beyond the current session to clear leftover state dependencies.

Why does autopilot resume state need to be preserved during dependency cleanup?▼

Preserving autopilot resume state during dependency cleanup allows the session to be resumed later, as the graceful cancellation pathway specifically protects autopilot data while clearing other active mode states.