Skip to content
reaatechREAATECH

reaatech/circuit-breaker-agents

0Last commit: May 12, 2026GitHub →

These packages provide a circuit breaker implementation designed for agent-to-tool and agent-to-agent communication, supporting confidence-based and cost-based tripping alongside standard error thresholds. You would adopt them to manage the reliability of LLM-based workflows by isolating tool failures and enforcing budget constraints across distributed environments. The system uses a lazy, timer-free state machine that can optionally persist state across process restarts using Firestore, DynamoDB, or Redis adapters.

Packages

7 packages

@reaatech/circuit-breaker-agents

v0.1.0
Provides a unified entry point that re-exports the `CircuitBreaker` class, state machine logic, and all persistence adapters from the core and persistence sub-packages. It serves as a drop-in replacement for the core library when you require distributed state management via Redis, Firestore, or DynamoDB.
status
published
published
2 days ago

@reaatech/circuit-breaker-core

v0.1.0
Provides a lazy-transitioning circuit breaker class for managing service-to-service communication via configurable trip and recovery strategies. It exposes an `execute` method for wrapping operations and requires only `zod` as a runtime dependency.
status
published
published
2 days ago

@reaatech/circuit-breaker-example-basic

pending npm
Description pending.
status
awaiting publish

@reaatech/circuit-breaker-example-dynamodb

pending npm
Description pending.
status
awaiting publish

@reaatech/circuit-breaker-example-firestore

pending npm
Description pending.
status
awaiting publish

@reaatech/circuit-breaker-example-redis

pending npm
Description pending.
status
awaiting publish

@reaatech/circuit-breaker-persistence

v0.1.0
Provides persistence adapters for circuit breaker state to enable cross-instance state sharing and survival across process restarts. It exports a standard `PersistenceAdapter` interface with implementations for Redis, Firestore, DynamoDB, and in-memory storage, each requiring its respective cloud SDK as a peer dependency.
status
published
published
2 days ago

Comments

Sign in with GitHub to comment and vote.

Loading comments…