You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I loved the way I could see how many tokens it used when doing work. Why don't I see it anymore? Is there a way to bring it back?
And it used to look like this:
Reacted by Beehive Innovations, Dmitry Polushkin, Inquisitive-ME, bl-ue, Tommaso A, Jeremy Janzen, Jacques, serge shima, Mark Rieck, Dawid Kowcuń and 40 more
Reacted by Artur Havrylov, Jacques, Beehive Innovations, bl-ue, Tommaso A, Mark Rieck, Johannes Ekman, freemind1992, Collin Wentzien, Benjamin Tebbutt and 16 more
instant downgrade.. not going to deal with this black box of no time elapsed and token display.
Reacted by Beehive Innovations, Artur Havrylov, Dawid Kowcuń, bl-ue, Aljosa Asanovic, freemind1992, Benjamin Tebbutt, Twango99, Collin Wentzien, duckSquirrelPilot and 5 more
Huge UX downgrade. Instead of having confirmation that it's working on something, I'm just wondering if it's stuck under the hood. Because it could be Boondoggling at times while the produced tokens remain at 0.
Reacted by 哈雷不灰心, Artur Havrylov, serge shima, Dmitry Polushkin, Bird, freemind1992, Orlando Osorio, Paul Roever, bl-ue, Benjamin Tebbutt and 10 more
@levpopov given the enormous amount of settings and customization CC already offers, why not make this customizable? The token counter makes a huge difference, this thread and the number of votes is a testament to that. Verbose is too verbose. Why would anyone want to use that mode unless debugging hooks / MCP services / bored?
Reacted by Lu, Wangshan, Peter Cole, Eric Busalacchi, VM, bl-ue, Nathaniel Furniss and mahnoorfirdous
Agreed, --verbose is not a suitable solution, it is not a mode you would like to run day to day (too much noise), perhaps useful for debugging, etc.
On the other hand, token counter is immensely useful - especially when dealing with flaky proxies, providers, etc.
PLEASE add option to bring it back, perhaps via statusline parameter or something like that.
Reacted by Peter Cole, Artur Havrylov, Eric Busalacchi, Mats Finsås, VM, bl-ue, mahnoorfirdous and FHT Mitchell
I agree that verbose mode is not a viable option, so I would not consider this issue resolved
Even if not bringing back the counter, you could explore alternatives which achieve a similar purpose. It seems most people on this thread weren't using this for actual token usage awareness. Some kind of loading indicator which animates only when tokens are being used would be a viable alternative for me and very welcome over what we have currently.
Thank you for the reports! The new UI is intentionally condensed, but you can still access the old behavior in verbose mode by running $ claude --verbose
I just want to see the token usage, not everything in verbose! Please let us configure it.
Reacted by VM, Eric Busalacchi, Dom, bl-ue, Artur Havrylov, Nathaniel Furniss and mahnoorfirdous
Hi everyone! We just added a feature to tweakcc to re-enable the token counter and the elapsed time automatically without having to run Claude Code with --verbose option. To try it out, just run npx tweakcc and select the top option, *Apply customizations to cli.js and then run claude. Enjoy!
Reacted by Ben Alkov, Eric Busalacchi, Pablo LION, Artur Havrylov and mahnoorfirdous
Reacted by Beehive Innovations, Artur Havrylov and Peter Cole
Claude code now faces intense competition from OpenAI codex. I have heard a lot of similar experiences from people who use both codex and claude code, that codex with gpt-5 high reasoning is better at handling problems than opus 4, while claude code has better UX. This UX request has a high number of upvotes (currently sits at 47), which if ignored will reduce the appeal of claude code's UX (maybe not significantly, but noticeably). People will jump ship if the UX of claude code is on par with codex.
Reacted by Aljosa Asanovic, bl-ue, Artur Havrylov, mahnoorfirdous, Peter Cole and Eric Busalacchi
This issue should not have been closed. The only reason you would recommend the verbose option as an alternative is if you intentionally do not want people to be able to best keep track of their tokens. I hope the intention is not to have billing rack up no matter what or limits to be exceeded quickly.
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.
Activity
github-actions commentedon Aug 16, 2025
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
[-]Token usage dissapared in @1.0.83[/-][+]Token usage dissapared in @1.0.82[/+]jacquesjg commentedon Aug 16, 2025
instant downgrade.. not going to deal with this black box of no time elapsed and token display.
guidedways commentedon Aug 16, 2025
The 'remaining context' count has been broken for several versions too along with this. Downgraded back to 1.0.71.
smixs commentedon Aug 17, 2025
Please, fix it and bring it back. Token counter now works only when Verbose Output is set to true.
raine commentedon Aug 17, 2025
I liked the token counter because it gave a sense of progress.
It's been boondoggling now for 30 seconds, how do I know if it's doing anything?
guidedways commentedon Aug 17, 2025
@raine in this particular example it's actually not meant to show you any progress /s
artnikbrothers commentedon Aug 17, 2025
Exactly! This is why I would like to have it back! I don't care too much about tokens, but rather about seeing the progress.
alasano commentedon Aug 17, 2025
Huge UX downgrade. Instead of having confirmation that it's working on something, I'm just wondering if it's stuck under the hood. Because it could be
Boondogglingat times while the produced tokens remain at 0.kirkouimet commentedon Aug 19, 2025
Yeah this needs to be added back, we have no clue if Claude is stalled out or if it is working
zhedream commentedon Aug 19, 2025
I need to display the time and token.
flowy11 commentedon Aug 20, 2025
+1
11 remaining items
guidedways commentedon Aug 22, 2025
@levpopov given the enormous amount of settings and customization CC already offers, why not make this customizable? The token counter makes a huge difference, this thread and the number of votes is a testament to that. Verbose is too verbose. Why would anyone want to use that mode unless debugging hooks / MCP services / bored?
nktl commentedon Aug 22, 2025
Agreed,
--verboseis not a suitable solution, it is not a mode you would like to run day to day (too much noise), perhaps useful for debugging, etc.On the other hand, token counter is immensely useful - especially when dealing with flaky proxies, providers, etc.
PLEASE add option to bring it back, perhaps via statusline parameter or something like that.
peterjcole commentedon Aug 23, 2025
I agree that verbose mode is not a viable option, so I would not consider this issue resolved
Even if not bringing back the counter, you could explore alternatives which achieve a similar purpose. It seems most people on this thread weren't using this for actual token usage awareness. Some kind of loading indicator which animates only when tokens are being used would be a viable alternative for me and very welcome over what we have currently.
embusalacchi commentedon Aug 23, 2025
Verbose is way too .. well verbose. Just let us add the counter back!
artnikbrothers commentedon Aug 23, 2025
I just want to see the token usage, not everything in verbose! Please let us configure it.
domvo commentedon Aug 25, 2025
Why is this issue closed? The problem has not been solved.
--verboseis not the same as it was before. Please give us a possibility to configure this.kirkouimet commentedon Aug 25, 2025
Agreed should be re-opened
Bring back the token counter and elapsed time metric
Bring back the token counter and elapsed time metric (#37)
bl-ue commentedon Aug 25, 2025
Hi everyone! We just added a feature to tweakcc to re-enable the token counter and the elapsed time automatically without having to run Claude Code with
--verboseoption. To try it out, just runnpx tweakccand select the top option,*Apply customizations to cli.jsand then runclaude. Enjoy!WiSaGaN commentedon Aug 25, 2025
Claude code now faces intense competition from OpenAI codex. I have heard a lot of similar experiences from people who use both codex and claude code, that codex with gpt-5 high reasoning is better at handling problems than opus 4, while claude code has better UX. This UX request has a high number of upvotes (currently sits at 47), which if ignored will reduce the appeal of claude code's UX (maybe not significantly, but noticeably). People will jump ship if the UX of claude code is on par with codex.
mahnoorfirdous commentedon Aug 26, 2025
This issue should not have been closed. The only reason you would recommend the verbose option as an alternative is if you intentionally do not want people to be able to best keep track of their tokens. I hope the intention is not to have billing rack up no matter what or limits to be exceeded quickly.
github-actions commentedon Sep 2, 2025
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.