Skip to content

Token usage dissapared in @1.0.82 #5929

Closed

Description

@artnikbrothers

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?

Image

And it used to look like this:

Image

Activity

  1. github-actions commented on Aug 16, 2025

    @github-actions

    Found 2 possible duplicate issues:

    1. Unreadable Text Color in Light Theme for /cost and /model Commands #4948
    2. Inconsistent Cost Reporting Across Platforms (Windows PowerShell) #5714

    This issue will be automatically closed as a duplicate in 3 days.

    • If your issue is a duplicate, please close it and 👍 the existing issue instead
    • To prevent auto-closure, add a comment or 👎 this comment

    🤖 Generated with Claude Code

  2. changed the title [-]Token usage dissapared in @1.0.83[/-] [+]Token usage dissapared in @1.0.82[/+] on Aug 16, 2025
  3. jacquesjg commented on Aug 16, 2025

    @jacquesjg

    instant downgrade.. not going to deal with this black box of no time elapsed and token display.

  4. guidedways commented on Aug 16, 2025

    @guidedways

    The 'remaining context' count has been broken for several versions too along with this. Downgraded back to 1.0.71.

  5. smixs commented on Aug 17, 2025

    @smixs

    Please, fix it and bring it back. Token counter now works only when Verbose Output is set to true.

  6. raine commented on Aug 17, 2025

    @raine

    I liked the token counter because it gave a sense of progress.

    Image

    It's been boondoggling now for 30 seconds, how do I know if it's doing anything?

  7. guidedways commented on Aug 17, 2025

    @guidedways

    @raine in this particular example it's actually not meant to show you any progress /s

    Boondoggling refers to doing work that appears to be useful or important but is actually wasteful, pointless, or serves little real purpose.

  8. artnikbrothers commented on Aug 17, 2025

    @artnikbrothers
    Author

    I liked the token counter because it gave a sense of progress.

    Image It's been boondoggling now for 30 seconds, how do I know if it's doing anything?

    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.

  9. alasano commented on Aug 17, 2025

    @alasano

    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.

  10. kirkouimet commented on Aug 19, 2025

    @kirkouimet

    Yeah this needs to be added back, we have no clue if Claude is stalled out or if it is working

  11. zhedream commented on Aug 19, 2025

    @zhedream

    I need to display the time and token.

  12. flowy11 commented on Aug 20, 2025

    @flowy11

    +1

  13. 11 remaining items

  14. ghost closed this as completedon Aug 22, 2025
  15. guidedways commented on Aug 22, 2025

    @guidedways

    @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?

  16. nktl commented on Aug 22, 2025

    @nktl

    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.

  17. peterjcole commented on Aug 23, 2025

    @peterjcole

    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.

  18. embusalacchi commented on Aug 23, 2025

    @embusalacchi

    Verbose is way too .. well verbose. Just let us add the counter back!

  19. artnikbrothers commented on Aug 23, 2025

    @artnikbrothers
    Author

    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.

  20. domvo commented on Aug 25, 2025

    @domvo

    Why is this issue closed? The problem has not been solved. --verbose is not the same as it was before. Please give us a possibility to configure this.

  21. kirkouimet commented on Aug 25, 2025

    @kirkouimet

    Agreed should be re-opened

  22. bl-ue commented on Aug 25, 2025

    @bl-ue

    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!

  23. WiSaGaN commented on Aug 25, 2025

    @WiSaGaN

    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.

  24. mahnoorfirdous commented on Aug 26, 2025

    @mahnoorfirdous

    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.

  25. github-actions commented on Sep 2, 2025

    @github-actions

    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.

  26. locked as resolved and limited conversation to collaborators on Sep 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:costarea:tuiquestionIssue is asking a question about how Claude Code works, or similar

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions