circuit-breaker

Autonomous loops are protected by implementing a circuit breaker pattern that detects stagnation and halts cycles showing no progress or repeated errors. This prevents resource exhaustion and accidental data corruption during automated tasks.

A circuit breaker pattern for API rate limits manages connection states across CLOSED, OPEN, and HALF-OPEN phases. It enforces configurable thresholds for error repetition and API limits, triggering a circuit break to halt operations when thresholds are exceeded.

Stop autonomous agents from deleting critical files by activating file protection mechanisms within the circuit breaker. These safeguards prevent accidental deletion of important configuration and project assets during autonomous refactoring loops.

A circuit breaker recovery protocol works by managing cooldown periods after a circuit breaks. Once the cooldown elapses, the system enters a HALF-OPEN state to probe for recovery and determine if the autonomous loop can safely resume operations.

Yes, you can configure stagnation detection thresholds for autonomous loops. The circuit breaker allows you to set specific limits for progress tracking, error repetition, and API rate limits to match your project's tolerance for stagnation.

No dependencies are required to run this circuit breaker for autonomous loop protection. It operates independently to monitor progress, enforce rate limits, and manage recovery protocols without external packages.