Cairn

MCP circuit breaker and tool budget hardening

NousResearch/hermes-agent · cluster 44172 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
6items grouped
Known?
Yes. 6 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 1 PR.

These items address MCP client reliability concerns including circuit breaker miscategorization of semantic errors, configurable per-server breaker thresholds, and missing limits on result size, per-turn call budgets, and reconnect constants. A related performance report describes uncapped tool call accumulation before a first response.

Open issues2

  • Issue#44172[Bug]: MCP client hardening: no result-size cap, no per-turn call budget, reconnect/circuit-breaker constants not configurable
  • Issue#67253[Perf]: No aggregate parent+subagent tool budget — Desktop catch-up turn ran 322 live tool calls before first response

Open PRs1

  • PR#68455feat(mcp): per-server circuit breaker threshold via breaker_threshold config

3 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1 · other 1

  • #61555 fix(mcp): semantic tool errors must not trip circuit breaker · done elsewhere → #109114, #74045, #75511, #11128
  • #74045 fix(tools): stop counting app-level MCP tool errors as server unreachability · other → #10447, #109180, #109245
  • #121227 fix(agent): bound delegated tool fan-out per turn · stale or abandoned → 0f2fdc2, 2304bf2, 5747548
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
agent
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/44172.json
cluster/44172.md