Cairn
NousResearch/hermes-agent

Parsing output token cap error messages in agent

Cluster 128171 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 PRs concern the agent's failure to parse certain output token limit error formats, which prevents the auto-clamp behavior from triggering. Multiple error message variants are being identified and handled.

Open issues1

  • Issue#128171[Bug]: 'max_tokens exceeds the limit of N' unparseable — output-cap auto-clamp never fires, every turn fails and the session auto-resets

Open PRs1

  • PR#128176fix(agent): parse common output cap errors

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #129737 fix(agent): parse direct comparison output cap error formats (#128171) · stale or abandoned
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/128171.json
cluster/128171.md