Cairn
NousResearch/hermes-agent

Agent redirect restart cap miscounts retries

Cluster 128000 · agent. Data as of

1 open item. Fix merged in #130528 on 1 Oct 2026. Check it covers your case.

The short answer

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

A bug where long interactive turns are incorrectly terminated because the redirect-restart counter shares or conflates its limit with the provider API retry count. The accompanying fixes separate redirect restarts from provider retries and reset the counter relative to the last response.

Open issues0

No open issues.

Open PRs1

  • PR#128004fix(agent): separate redirect restarts from provider retries

Fixes on record

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

  • #130528 Effectful tool calls refuse cut-short compression markers, and mid-turn corrections no longer end long turns (#128000, salvage #127613, #128682)

    merged to main

    files: agent/compression_marker.py, agent/conversation_loop.py, agent/tool_dispatch_helpers.py, agent/turn_iteration_prep.py, tests/agent/test_tool_call_guardrail_runtime.py, tests/agent/test_turn_iteration_prep.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #128682 fix(agent): count restarts since the last response toward the redirect cap · merged via another change → d486ba0, #130528
Closed issues · 1
  • Closed#128000[Bug]: long interactive turns end as loop_error ("Hermes got stuck in a loop") — the redirect-restart cap reuses agent.api_max_retries, so mid-turn user messages kill the turn
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.50: 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
#130528
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.

cluster/128000.json
cluster/128000.md