the /status command in discord does not display current session tokens but i believe the total tokens from all sessions.
this 1 hour session was reported as 68 million tokens
#discord reports wrong tokens for current sessions /status command
indigo wagon
minor ether
That number is misleading, but it does not look like /status is summing every session together.
The current /status path reads the SQLite row for the active Discord session ID and displays the persisted token buckets from that row. The confusing part is that the Tokens line is cumulative API usage for that session, not the number of tokens currently sitting in the context window.
So in a tool-heavy coding session, that number can climb very fast because each model call includes the current conversation/tool context again. A one-hour session can have much higher cumulative usage than the visible context size.
There is also a display cleanup we should make here: /status should probably call this Session usage or show current context separately, because Tokens reads like “current context tokens.” For now, treat that line as cumulative usage for the current session, not current context size and not all sessions combined.
I opened the small display cleanup for this here:
https://github.com/NousResearch/hermes-agent/pull/34967
It keeps the existing accounting behavior, but renames the /status line from Tokens to Session usage (cumulative) so it is clearer that the number is accumulated API usage for that active session, not current context size and not a total across all sessions.
cc @rocky oasis or @wild bison (review?)
