cancel-deep

Cancel active deep loop sessions by updating the session state file.

Updated Jan 23, 2026

Search Tags:#session-management #claude-code #development-workflow #autonomous-development #state-cleanup #cancel-deep #deep-loop

Ready to run

npx skills add https://github.com/marcusgoll/deep-loop-plugin --skill cancel-deep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cancel-deep
Source: https://github.com/marcusgoll/deep-loop-plugin/tree/main/skills/cancel-deep
Command: npx skills add https://github.com/marcusgoll/deep-loop-plugin --skill cancel-deep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of safely aborting an in-progress deep loop development session without losing session history or corrupting your project's git state.

Core Features & Use Cases

Safe Session Termination: Immediately marks an active deep loop as cancelled in the state file while preserving the full .deep session history.
Automatic Control File Cleanup: Removes leftover loop control files like FORCE_EXIT, NEEDS_USER, and RALPH_HANDOFF to reset the development environment.
Zero Side Effects: Does not modify your git state or delete the .deep directory, and is safe to run even if no deep loop is currently active.
Use Case: If you triggered a deep loop by mistake or need to pause it to address an urgent production issue, use this Skill to stop the session cleanly without disrupting your workflow.

Quick Start

Use the cancel-deep skill to immediately stop any active deep loop session and clean up its control files.

Frequently Asked Questions about cancel-deep

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

FAQPage Schema

How do I safely cancel an active deep loop session in Claude Code?▼

To safely cancel an active deep loop session, you mark the session state file as terminated. This process preserves your complete .deep session history and git state while cleaning up residual loop control files.

How do I stop autonomous development workflows without losing session history?▼

You can stop autonomous development workflows by updating the session state file to cancelled. This terminates the deep loop immediately while ensuring all historical session data in the .deep directory remains intact.

Does canceling a deep loop development session modify my git state?▼

Canceling a deep loop development session does not modify your git state. The cancellation process only updates the session state file and removes control files like RALPH_HANDOFF, leaving your repository untouched.

What happens to control files when I abort an in-progress deep loop?▼

When you abort an in-progress deep loop, residual control files including FORCE_EXIT, NEEDS_USER, and RALPH_HANDOFF are automatically removed. This cleanup resets your development environment without deleting the .deep directory.

Can I run a deep loop cancellation command if no session is currently active?▼

You can safely run the deep loop cancellation command even if no session is currently active. The process has zero side effects and will simply reset the environment by checking for and removing any residual control files.