# NousResearch/hermes-agent · Token count not saved to session database

## Open now

- 2 issues, 0 PRs open on GitHub.
- #47201: messages.token_count column is defined but never populated (always NULL)
- #58719: Cron sessions should persist per-message token_count to state.db
- _Broad area: open items may be separate problems._

The token_count column for assistant messages exists in the schema but is never written to the database. These issues and fixes address persisting per-message token counts to the session state store.

## TL;DR

- 3 member(s): 2 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.45`: the share of member 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.

## Open related issues

- #47201: messages.token_count column is defined but never populated (always NULL)
- #58719: Cron sessions should persist per-message token_count to state.db

## Prior & competing PRs

- **#58846: fix: persist assistant message token_count to session DB**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#47424`, `#47424`

## Fix status

- No merged fix on record.
- Subsystem: `agent`