Repository navigation
Feature Request: Restore Time & Token Indicators + Add Context Usage Display #7111
Description
Description
Claude Code needs two types of improvements for better user experience:
Restore Previously Removed Features:
- Time elapsed indicator - Shows how long Claude Code has been working on the current task
- Token consumption counter - Displays tokens used for the current operation
Add New Feature:
3. Context usage percentage - Shows current context window utilization
Why These Matter
- Time tracking helps users understand task complexity and duration patterns
- Token visibility enables users to optimize prompts and understand cost implications for different task types
- Context percentage allows proactive context management instead of reactive auto-compacting
Current Problem
Without the context usage indicator, users can't make informed decisions about when to clear or compact. This leads to:
- Continuing with tasks when context is nearly full, causing mid-task interruptions
- Unnecessary clearing when context usage is still low
- Poor user experience due to unexpected auto-compact triggers
Request
- Restore the time and token indicators that were previously available
- Add context usage percentage display
Codex currently has all of these features and they significantly improve the user experience by providing transparency and enabling better resource management.
These indicators transform context management from guesswork into informed decision-making.
Reacted by Paul Clegg, JB Rx, bobbywang, Adam Gyarmati, Mark, Kyle Howells, Jean-Sébastien B., Philippe Scorsolini, Jenova-Marie, Aron Lomner and 14 more
Activity
github-actions commentedon Sep 4, 2025
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
jb-rx commentedon Sep 4, 2025
The "context usage percentage display" would be great ! In Cline I like to see how much context is filled and then decide if it is a good moment to trigger compaction.
BobbyWang0120 commentedon Sep 4, 2025
Yes, Codex, Cline and Cursor they all have this functionality, and actually Claude Code will dynamically show how much context left when it want to auto-compact, so it should be easy for them to just show the indicator all the time instead of only when you approach the limit, not sure why they don't do that and what makes them decide that.
github-actions commentedon Dec 6, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Aron-Lomner commentedon Jan 5, 2026
Requiring a command that consumes context in order to view context, is something I would only expect from someone who vibe coded their UX design.
davidalee commentedon Feb 3, 2026
I'd also like this feature. I am constantly doing
/contextmaybe 3-4 times every session which ironically eats up more context.The popularity of this repo should indicate just how in-demand this feature is.
wrone commentedon Apr 2, 2026
+1
leopoliveira commentedon Apr 7, 2026
Nothing new on this?
Endzel commentedon May 13, 2026
Why is this not pushed further?
Seems like a simple feature, currently achievable externally though it would look like a great addition to the base product that could help all users plan and refine their usage accordingly 🙏🏼
junaidtitan commentedon May 13, 2026
Until this gets built in, Cozempic gives you token estimation and context visibility right now. The
cozempic doctorcommand shows session size, token count, and bloat sources, and the guard daemon continuously reports context utilization so you can manage proactively instead of waiting for auto-compact.pip install cozempic— auto-wires on first run. https://github.com/Ruya-AI/cozempic — happy to hear if the visibility helps with planning.junaidtitan commentedon May 13, 2026
Until this gets built in, Cozempic's
estimate_tokenscommand gives you a breakdown of where your context tokens are going — tool results, thinking blocks, images, metadata, etc. It helps you understand what's eating your context window so you can act proactively. Also available as an MCP tool in the plugin.pip install cozempic && cozempic estimateto try it. Repo: https://github.com/Ruya-AI/cozempic — let me know if the breakdown is useful.dagelf commentedon May 18, 2026
Anthropic has a strong incentive to make usage feel lightweight in the UI, but the default display is incomplete in offering only limited context indicators that don't fully break down input/output/tool costs or provide persistent live totals. This can lead users to underestimate spend and more importantly for model and output improvement: underthink their inputs, especially given how quickly agentic tool use and context re-reading accumulate.
Reporting or emphasizing only parts of the picture feels like omission when billing covers everything.
This seems at odds with Claude's principles of being maximally helpful and honest with users. A live token usage display with clear input/output/cache/estimated cost breakdown (similar to what many users end up hacking together, or what competitors like Cursor offer) would build far more trust and let people manage their sessions proactively.
Even small transparency wins matter for a billion-dollar company. Doing the right thing here signals that customers are held in high regard, not as an afterthought.
Tools like
/context,/usageand/costare provided, but I would like a billion dollar company to lead by example in defeating the tyranny of the default.Better examples elsewhere: Cursor gets a lot of praise for superior context usage visibility and management in comparisons (e.g., clearer indicators, better control via @mentions/rules). OpenAI's playground and dashboards often feel more upfront with counters. Third-party ecosystems (ccusage, custom statuslines) fill the gap effectively. All of these validate this issue.
junaidtitan commentedon May 30, 2026
In case it helps in the meantime — cozempic (github.com/Ruya-AI/cozempic) surfaces exact token usage (input + cache + output, read from the usage frames so it matches the real context) plus a context % bar and cache-hit rate via
cozempic current --diagnose. It's primarily a context-pruner, but the measurement is accurate. Free/open-source. Would genuinely appreciate feedback on whether that readout covers what you're missing here.bcherny commentedon Aug 17, 2026
These are available today: run
/contextfor a breakdown of context window usage, and use a status line to show context percentage, session duration, and cost continuously — the status line input includescontext_window.used_percentage,cost.total_duration_ms, andcost.total_cost_usd./costand/usagealso show token/cost totals. Docs: https://code.claude.com/docs/en/statusline and https://code.claude.com/docs/en/context-windowClosing as available; open a new issue if a specific indicator is still missing.
🤖 Generated with Claude Code
github-actions commentedon Oct 7, 2026
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.