NousResearch/hermes-agent

Guardrails: escalating repeated tool-call failures and loops to blocking

Cluster 32827 · agent. Data as of 2026-10-26 12:29 UTC

1 open item. Fix merged in #100967 on 2 Sep 2026. Check it covers your case.

open issue

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 0 issues already closed.
Fix event: A fix was merged to main in PR #100967. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 1 issue and 0 PRs.

Next step: read #100967, then check whether your report is the one still open.

Read #100967 Pick up a Lab task

These members share a theme: guardrail behavior around repeated same-tool failures or tool-call loops, including a report that a warning does not escalate to a block and two pull requests proposing auto-blocking or hard-stops. The titles do not show whether any of these changes were merged or have any effect.

Open issues1

Issue#32827[bug] same_tool_failure_warning does not auto-escalate to block; allows unbounded retry-loop cost amplification

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#100967 fix(guardrails): tool-call loops hard-stop on unattended platforms, identical replays halt for any tool (#49075, #89069; salvage #49189, #47231)

merged to main

files: agent/agent_init.py, agent/tool_guardrails.py, cli-config.yaml.example, hermes_cli/config_defaults.py, run_agent.py, tests/agent/test_tool_guardrails.py, tests/run_agent/test_tool_call_guardrail_runtime.py, website/docs/user-guide/configuration.md, website/docs/user-guide/docker.md

1 PR closed without merging

From the close comments: done elsewhere 1

#54340 fix(guardrails): auto-block same-tool failures to prevent cost-amplification loops (#32827) · done elsewhere → 25d954c, #100967

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

Subsystem: agent
Merged PRs: #100967
Closed issues: 0
Attempts: 1 PR closed without merging
Fix link checked: 2 Sep 2026

For your agent

The same facts, typed.

cluster/32827.json
cluster/32827.md