Tool-call loop guardrail halt and recovery behavior
NousResearch/hermes-agent · cluster 53959 · agent
Data as of
3 open items. Fix attempted, not merged.
The short answer
2open issues
1open PR
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs concern how the agent handles tool-call loop guardrail triggers, specifically whether a hard stop should silently halt the task or first give the model an opportunity to recover or use fallback strategies before ending the turn.
Open issues2
Open PRs1
- PR#92433fix(agent): rebound once after blocked tool batch
1 PR closed without merging
From the close comments: stale or abandoned 1
- #64363 fix(agent): let guardrail hard-stop give the model one rebound before halting · stale or abandoned
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.39: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging