messages.token_count not populated with completion tokens

NousResearch/hermes-agent · cluster 136851 · 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.

One issue reports that the messages.token_count column is NULL for every row even though a writer and reader exist. Two pull requests propose stamping each response's completion tokens onto the assistant message row; their actual effect is not established by the titles.

Open issues1

  • Issue#136851[Bug]: messages.token_count is never written — the column is NULL for every row in every session, though both the writer and the reader are implemented

Open PRs2

  • PR#136879fix(agent): stamp the response completion tokens onto its assistant row
  • PR#137149fix(agent): stamp messages.token_count from each response's completion tokens
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.