cc-ralph

Automate unattended task execution across multiple Claude sessions by running an autonomous execution loop that spawns fresh contexts per iteration, preventing context bleed. This approach uses receipt-based verification to validate progress and ensure traceable task completion without manual intervention.

Context pollution occurs when a single session accumulates irrelevant state over long iterative workflows. Prevent it by spawning fresh Claude sessions per iteration, ensuring clean execution contexts for each task cycle while maintaining verifiable progress through receipt-backed proof-of-work.

Yes, multi-model review gates can verify plan, work, and completion stages in autonomous workflows. These review gates act as safety hooks within the execution loop, validating task quality and ensuring risk-guarded automation before proceeding to the next iteration.

Yes, cc-work and cc-teams are required dependencies to run unattended automation loops with safety guards. These provide the foundational orchestration and multi-team coordination needed for end-to-end epic execution and configurable loop controls.

Validate task completion in an autonomous execution loop using receipt-based proof-of-work. Receipts validate that each iteration has produced verifiable progress, ensuring risk-guarded automation with safety hooks and sentinels has successfully finished before advancing.

Initialize an autonomous execution loop with configurable sentinels by running the ralph.sh script after setup. This starts the main loop, applying safety guards and sentinel controls for unattended operation while managing end-to-end epic execution across multiple sessions.