Cairn
NousResearch/hermes-agent

Fix misclassified stream endings with usage-only final chunks

Cluster 91373 · agent. Data as of

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

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #100515. 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
Nothing open on GitHub.

These items address a bug where spec-compliant streams ending with a usage-only chunk (no finish_reason) are incorrectly treated as mid-stream disconnections. The fix prevents erroneous 'continue' nudges being injected into otherwise complete responses.

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.

  • #100515 fix(streaming): complete Portal/vLLM streams no longer misread as mid-stream drops (#90848, #91373; salvages #91189, #91376, #96333)

    merged to main

    files: agent/chat_completion_helpers.py, contributors/emails/[redacted:email], hermes_cli/proxy/server.py, hermes_cli/proxy/sse_done.py, tests/hermes_cli/test_proxy.py, tests/hermes_cli/test_sse_done.py, tests/run_agent/test_partial_stream_finish_reason.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #91376 fix(stream): do not misclassify stream with final usage chunk as mid-stream drop — closes #91373 · merged via another change → 6ddafd3, #100515, #91189, #96333
Closed issues · 1
  • Closed#91373`include_usage` makes the final chunk usage-only (no `finish_reason`) per OpenAI spec — hermes misreads spec-compliant vLLM streams as network cuts, injecting fake "continue" nudges
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
#100515
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
1 Sep 2026

For your agent

The same facts, typed.

cluster/91373.json
cluster/91373.md