ralph-cancel

Stop an active Ralph loop and archive its state file.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/khides/research-boilerplate --skill ralph-cancel-khides
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-cancel
Source: https://github.com/khides/research-boilerplate/tree/main/.claude/skills/ralph-cancel
Command: npx skills add https://github.com/khides/research-boilerplate --skill ralph-cancel-khides

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops an active Ralph loop and archives its state for safe cleanup.

Core Features & Use Cases

  • Gracefully terminate a running Ralph session and prevent partial state from persisting
  • Archive the current state file with a timestamp for auditing and recovery
  • Remove the active session references to avoid orphaned state and ensure a clean restart

Quick Start

Cancel the active Ralph loop and archive its state.

Frequently Asked Questions about ralph-cancel

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

FAQPage Schema
How do I safely cancel an active Ralph loop and preserve session state?

To cancel an active Ralph loop and preserve session state, stop the running session and archive the current state file with a timestamp for auditing. This removes active session references to prevent orphaned state.

What happens to the state file when I terminate a Ralph session?

When you terminate a Ralph session, the active state file is archived with a timestamp for recovery and auditing. Active session references are then removed to ensure a clean restart without orphaned data.

How do I clean up orphaned state from a terminated Ralph experiment?

To clean up orphaned state from a terminated Ralph experiment, archive the current state file and remove the active session references. This prevents partial state from persisting and ensures a clean restart.

Do I need CLAUDE_SESSION_ID to archive Ralph state for auditing?

Yes, the process relies on CLAUDE_SESSION_ID to locate the session. It reads the path of the active state file, archives the state for auditing, and removes the active references for safe cleanup.

When should I archive Ralph state instead of deleting it directly?

You should archive Ralph state when gracefully terminating ongoing experiments where state must be preserved for auditing and recovery. Archiving with a timestamp prevents data loss compared to direct deletion.