Cairn
NousResearch/hermes-agent

Per-operation retry limit feature design and implementation

Cluster 18504. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These members concern a proposed and in-progress feature to add per-operation retry limits to the agent, including a consecutive call circuit breaker. Multiple pull requests and a feature request track the design and implementation of this capability.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: partial fix 1 · other 1

  • #18585 feat(agent): per-operation retry limit and consecutive call circuit breaker · partial fix
  • #21208 feat(agent): per-operation retry limit + setup wizard surface (salvage #18585) · other → #18585, #18504
Closed issues · 1
  • Closed#18504Feature Request: Per-Operation Retry Limit
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: 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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/18504.json
cluster/18504.md