claude-code - 💡(How to fix) Fix [BUG] Running token counter is dismissed when input is focused and cannot be recalled [1 comments, 2 participants]

Describe the bug

The token counter displayed during Claude's response disappears as soon as the user focuses the input field to type their next prompt. Once dismissed, it cannot be recovered — there is no way to see the final token count for the just-completed turn short of inspecting the raw JSONL session file under ~/.claude/projects/.

This makes the counter effectively unmonitorable during normal use: the only moment to read it is the narrow window between Claude finishing a response and the user clicking into the input box, which is not how anyone naturally works.

Expected behavior

The counter should either persist while the input field is focused, or be accessible on demand — for example, via the Plan usage panel (already accessible by clicking the context window indicator).

Actual behavior

Counter disappears on input focus. No recall path exists in the UI. The Plan usage panel shows aggregate limit consumption but not the per-turn execution counter.

Impact

Users trying to track consumption turn-by-turn have no reliable way to do so through the UI. The only alternative — parsing JSONL session files — is not a viable path for most users and is highly disruptive even for those who know the files exist.

This compounds #55121, which reports that the counter already undercounts sub-agent consumption. Even if that undercounting is fixed, the information is inaccessible if the counter can't be held open long enough to read.

Prior art / not a duplicate

#31059, #49078, and #42808 are all closed as duplicates of each other and address persistent display of usage/token information in the footer. Those requests are in the vicinity but are feature requests for a persistent indicator — a different ask from this bug report, which is specifically that an existing counter is non-recoverably dismissed during normal use.