NousResearch/hermes-agent

Streaming repetition loop detection and cutoff

Cluster 127234. Data as of

Nothing open on GitHub. Fix merged in #130551 on 1 Oct 2026. Check it covers your case.

The short answer

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

These items concern a bug where repetition loops during streaming responses would not be detected or terminated until the stream finished. The fixes address cutting runaway repetition loops mid-stream, with and without callbacks.

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.

  • #130551 fix(agent): a model stuck in a repetition loop no longer streams forever on an uncapped endpoint (#127234, salvage #127242)

    merged to main

    files: agent/chat_completion_helpers.py, agent/repetition_guard.py, agent/turn_truncation.py, tests/agent/test_stream_runaway_repetition.py, website/docs/integrations/providers.md, website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/integrations/providers.md

2 PRs closed without merging

From the close comments: merged via another change 1 · partial fix 1

  • #127242 fix(agent): cut a runaway repetition loop while it streams, callback or not · partial fix → 53dcaec, bc7f58f, #127234
  • #129709 fix(agent): end streaming repetition loops live at runaway scale (#127234) · merged via another change → 77c373a, #127234, #127242, #130551
Closed issues · 1
  • Closed#127234[Bug]: A streaming repetition loop never ends on an uncapped endpoint — every repetition check waits for the stream to finish
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

Merged PRs
#130551
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
1 Oct 2026

For your agent

The same facts, typed.