Show HN: Circuit Breaker – runtime cost ceilings for AI agents
Circuit Breaker is a minimal wrapper designed to manage the execution of AI agents by enforcing runtime cost ceilings. It offers two modes: budget-guard, which caps token usage, and loop-killer, which detects repeated states. The tool is framework-agnostic and allows for easy integration with various AI frameworks.
- ▪Circuit Breaker can cut execution short once usage crosses a specified limit.
- ▪It provides options to reject oversized prompts before they are sent to the AI provider.
- ▪The tool emits events during execution to track its performance and state.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,312 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/MonetiseBG/circuit-breaker |
| Publication time | Tue, 19 May 2026 14:07:43 +0000 |
| Retrieval time | 2026-05-19T14:19:57.683Z |
| Last seen | 2026-05-19T14:19:57.683Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | woY721Iw8Yue |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
@monetisebg/circuit-breaker One wrapper between you and runaway execution. Minimal circuit breaker for AI agents. Wrap any supported agent and pick a mode — the breaker cuts the run short once provider-reported usage crosses a limit, and (optionally) refuses an oversized prompt before it is even sent. Zero-config: defaults work out of the box. Two modes, pick one: budget-guard (token caps) and loop-killer (state-repeat detection). Post-hoc enforcement by default: token tripping happens after each call or turn boundary, so the call that crosses the limit still counts. Use the optional estimateInputTokens preflight (see below) to reject oversized initial inputs before any provider work happens. Visible: emits CircuitBreakerEvents as the run progresses.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.