Token usage dissapared in @1.0.82

Found 2 possible duplicate issues:

1. https://github.com/anthropics/claude-code/issues/4948
2. https://github.com/anthropics/claude-code/issues/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

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

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

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

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

<img width="552" height="62" alt="Image" src="https://github.com/user-attachments/assets/7ebb5259-0898-4136-bae8-eeafa32de427" />

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

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

I liked the token counter because it gave a sense of progress. <img alt="Image" width="552" height="62" src="https://private-user-images.githubusercontent.com/11027/478778096-7ebb5259-0898-4136-bae8-eeafa32de427.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTU0NjczMjgsIm5iZiI6MTc1NTQ2NzAyOCwicGF0aCI6Ii8xMTAyNy80Nzg3NzgwOTYtN2ViYjUyNTktMDg5OC00MTM2LWJhZTgtZWVhZmEzMmRlNDI3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA4MTclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwODE3VDIxNDM0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTUwZWVjY2U0NjFjYTQ2YzFmNjAzM2U0MTRmOTE1NWJiMzNmMDBlYjljNDJmMWI5YmZkZDNiYTRjYjY0MDIxMjMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.gCdCn7j-JSgnFoX3f0uR9aJRwW5Z3GZLNhwu8LP2OI4"> 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.

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.

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

I need to display the time and token.

+1

+1 on this. To give more context about why this is an issue, on top of the points already made about giving a sense of progress, the token counter just gave you something to look at in order to main concentration on the task.

It sounds like a stretch, but I genuinely believe that not having this to look at has an outsized impact on my productivity, because the cost of the context switching which results from getting distracted while the tool is working is very large. It was one of the reasons I preferred Claude Code to other tools.

+1 I tried statusline but no help

The realtime token counter / timer was extremely valuable feature of CC, so be able to see that it is doing things for you and not stuck or bogged down e.g. by wonky corporate proxy. Please bring it back!

Seconding this, I'm also seeing #5951 occurring also where it just shows 'undefined' and that's it. Really infuriating.

<img width="750" height="138" alt="Image" src="https://github.com/user-attachments/assets/2ac7939a-a92b-4707-b7ce-8e968143fd1f" />

Seconding this, I'm also seeing #5951 occurring also where it just shows 'undefined' and that's it. Really infuriating. <img alt="Image" width="750" height="138" src="https://private-user-images.githubusercontent.com/11824150/480066585-2ac7939a-a92b-4707-b7ce-8e968143fd1f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTU3MDA4MDAsIm5iZiI6MTc1NTcwMDUwMCwicGF0aCI6Ii8xMTgyNDE1MC80ODAwNjY1ODUtMmFjNzkzOWEtYTkyYi00NzA3LWI3Y2UtOGU5NjgxNDNmZDFmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA4MjAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwODIwVDE0MzUwMFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTkzZDYxZWRjNDliODNkMTgzMGNjZmQ1MTA1YmQ2MjhmOTY4ZTM5YzU2Y2I1Yjc3MjFlNDQ0NTBhYjQ3Yzc2ZGImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.-kjKgE-n170Jhwq4_eTyneR9R__6_HnlbZiGPJcoArA">

It would be more meaningful if it said "undefining..." 😄

I believe these recent issues are bugs and not intentional. You can tell they've slowed down on the rapid updates they were pushing last week. Potentially preparing for the 1M context plus other goodies and will drop a more substantial update soon (with this and much more fixed).

@guidedways that's a bit optimistic, no? its kind of a big bug to just lose a key piece of data that's been here the whole way, and meanwhile force tips on long time users also?

Meanwhile we have status bar to configure with no useful defaults?

If this is what you get from slowing down changes, they should go back to faster iteration.

@guidedways that's a bit optimistic, no? its kind of a big bug to just lose a key piece of data that's been here the whole way, and meanwhile force tips on long time users also? Meanwhile we have status bar to configure with no useful defaults? If this is what you get from slowing down changes, they should go back to faster iteration.

As others have pointed out, for now a viable option is to downgrade to a version such as 1.0.71 and wait it out. I'm optimistic because CC has thus far proven to lead the way and set an excellent example for everyone else to follow. This is just an unfortunate glitch that went under the radar. Stuff like this has happened before in the early days of 0.x.

Version 1.0.86 released - still no fixes to the token counter. It sucks

> @guidedways that's a bit optimistic, no? its kind of a big bug to just lose a key piece of data that's been here the whole way, and meanwhile force tips on long time users also? > > Meanwhile we have status bar to configure with no useful defaults? > > If this is what you get from slowing down changes, they should go back to faster iteration. As others have pointed out, for now a viable option is to downgrade to a version such as 1.0.71 and wait it out. I'm optimistic because CC has thus far proven to lead the way and set an excellent example for everyone else to follow. This is just an unfortunate glitch that went under the radar. Stuff like this has happened before in the early days of 0.x.

I downgraded to 1.0.81 and it has the token counter. So I use this version until it's fixed

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

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

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.

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.

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

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.

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.

Agreed should be re-opened

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!

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.

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.