NousResearch/hermes-agent

Agent loop-detector ignores volatile execution metadata

Cluster 124072. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #124724 on 27 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #124724, then check it covers your case.

Read #124724 Pick up a Lab task

These items address a bug where volatile or per-call metadata (such as execution timestamps or transient fields) was included in the loop-detection hash, causing the agent to fail to recognize repeated tool results as loops. One report documents a severe real-world consequence: a wait loop for background subagents ran to the iteration ceiling, wasting 190 calls over 84 minutes before human intervention.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

#124724 fix(agent): ignore execute_code per-call metadata in the loop-detector result hash

merged to main

files: agent/tool_guardrails.py, contributors/emails/[redacted:email], tests/agent/test_tool_guardrails.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#124276 fix(agent): ignore volatile execution metadata in tool-result loop hash · superseded by another PR

Closed issues · 1

Closed#124072[Bug]: Waiting on background subagents can deadlock a turn — execute_code-only wait loop ran to the iteration ceiling with zero guard activity (84 min, 190 wasted calls, human abort)

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

Merged PRs: #124724
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 27 Sep 2026

For your agent

The same facts, typed.

cluster/124072.json
cluster/124072.md