Cairn
NousResearch/hermes-agent

MiniMax streaming token usage gaps and fixes

Cluster 60683 · agent. Data as of

Nothing open on GitHub. Fix merged in #121554 on 24 Sep 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 #121554. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #121554. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs center on missing or null usage data during Anthropic-compatible streaming with MiniMax and similar providers, along with proposed and attempted fallback estimation approaches. A secondary thread involves adding MiniMax-M3 model support and related logging improvements.

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.

  • #121554 fix(anthropic): normalize usage:null streams, non-stream fallback on out-of-order SSE, Messages-shaped partial stubs

    merged to main

    files: agent/anthropic_adapter.py, agent/chat_completion_helpers.py, tests/agent/test_anthropic_stream_fallbacks.py, tests/agent/test_streaming.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #60695 fix(agent): fall back to messages.create on Anthropic stream usage aggregation errors · merged via another change → 44f6d3b, #121554, #60683
  • #60700 fix(provider): catch AttributeError on output_tokens in Anthropic stream fallback · done elsewhere → 44f6d3b, #60683, #121554
Closed issues · 1
  • Closed#60683[Bug]: MiniMax Anthropic stream crashes with 'NoneType' object has no attribute 'output_tokens' in get_final_message()
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
#121554
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/60683.json
cluster/60683.md