Cairn
NousResearch/hermes-agent

Token counting on truncated or incomplete API responses

Cluster 38458 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

These items address token usage not being recorded when API calls encounter errors or responses are truncated due to length limits. Related changes also cover refunding call counts when retries are exhausted.

Open issues1

  • Issue#38458[Bug]: The token consumed is not counted if the api call fails for "length" reason.

Open PRs2

  • PR#38460fix(conversation): count tokens from length-truncated responses
  • PR#38553fix(agent): track tokens on truncated responses and refund api_call_count on retry exhaustion
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/38458.json
cluster/38458.md