[BUG] Desktop Code tab: running agents no longer show elapsed timer, token count or context-window usage
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Since the Claude Desktop update released on Oct 14, 2026, the Code tab no longer shows, for running agents/subagents:
- the elapsed-time timer
- the live token count
- each agent's context-window usage
There is no setting to bring them back, and no release note mentions their removal.
What Should Happen?
Each running agent should show its elapsed time, token count and context-window usage, as it did before the update.
Error Messages/Logs
Steps to Reproduce
- Update Claude Desktop to 2.37337.1
- Open the Code tab and start a session
- Ask Claude to spawn one or more subagents
- Look at the running agents: no timer, no token count, no context usage
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
The Claude Desktop version installed before the Oct 14, 2026 update
Claude Code Version
Claude Desktop 2.37337.1 (Windows)
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
Related, not duplicates: #102094 and #102103 (main-session context window missing since the same update), #99678 (subagent token counts missing in Desktop, Oct 5), #71642 (same per-agent regression in the CLI).
This per-agent visibility is how I decide when to stop, compact or restart an agent. Without it, I'm running agents blind.
4 Comments
Confirming this on Windows 11 (10.0.26200).
2.37337.1, bundled Claude Code2.1.2952.31226.1showed per-subagent token counts in the background tasks view. After the update on Oct 14 it no longer does.2.1.295before and after), so this looks like a desktop UI regression rather than a CLI change.A workaround while this is missing: the live numbers are still written to the transcripts, so they can be shown outside the app. Each agent and subagent has its own
.jsonlunder~/.claude/projects/<project>/(Windows:%USERPROFILE%\.claude\projects), and every model call logs input, cache read/write and output tokens.npx github:lowkey-studio/quotatrace live(a free, local, zero-dependency tool I maintain; disclosure: mine) tails those files in a second terminal. For each running agent and subagent it shows tokens per minute, calls, current context size and cache hit rate, refreshed every 5 seconds. It doesn't show elapsed time per agent yet. https://github.com/lowkey-studio/quotatrace. +1 for restoring it in the app, though.One more detail dropped by the same Oct 14 update: the Background tasks panel rows no longer show which model is running each task. Before, you could tell at a glance which tasks were on cheaper models and which were on Opus; now you have to open each task one by one to find out. Same pattern as the timer/token/context regression: the information clearly still exists, it's just no longer surfaced on the row. Please restore the per-task model label along with the timer, token count and context usage.
I second this ticket too.
Just put the small context window bar back, keep the expanded one in the side bar or whatever. I'm gonna use https://github.com/JiahaoXu10Arthur/context-band until it's fixed (another ribbon).
The circular indicator was fine, now it's useless. Put two circles then, one for context, one for 5 hour session.
I've already had Claude auto compacted 20 sessions, in the middle of a session, I am completely blind with this too.
Normally I do manual compact, but I haven't gotten around to using it because I can't see it on the ring or in the menu as usual.
Commit ribbon was useful. You know what's not useful? A ribbon telling me I'm running out of my 5 hour limit when there's a circle with yellow color right there.
And the "You're on course to spend your weekly limit", that's a useless ribbon because I can click the circle and see exactly what my weekly limit is.
Congrats to shittification 2026
But I had Anthony Morris tell me that "it lives in the side ribbon now", thanks, that's where I wanted it on my non 4K monitor...