Cairn
NousResearch/hermes-agent

max_completion_tokens parameter support for specific models

Cluster 37151 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These issues and pull requests address using the correct max_completion_tokens parameter for MiniMax and GPT-5/o-series models instead of the legacy max_tokens parameter. The changes target specific model families and provider paths to ensure proper token limit handling.

Open issues1

  • Issue#37151_max_tokens_param should use max_completion_tokens for MiniMax models

Open PRs1

  • PR#37152fix(agent): use max_completion_tokens for MiniMax

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #43163 fix(agent): use max_completion_tokens for gpt-5.x and o-series models regardless of provider path · done elsewhere → 19c07c4
  • #124204 fix(params): use max_completion_tokens for MiniMax OpenAI-compat (#37151) · other
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
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/37151.json
cluster/37151.md