claude-code - 💡(How to fix) Fix Surface context-window usage as a persistent indicator in the VS Code extension [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52156Fetched 2026-04-23 07:35:09
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Timeline (top)
labeled ×3commented ×1

The Claude Code terminal TUI shows a continuous context-window usage indicator (percent remaining), which makes it easy to know when to run /compact or /clear. The VS Code native extension does not surface this information persistently — users have to run /context on demand to check.

Root Cause

The Claude Code terminal TUI shows a continuous context-window usage indicator (percent remaining), which makes it easy to know when to run /compact or /clear. The VS Code native extension does not surface this information persistently — users have to run /context on demand to check.

RAW_BUFFERClick to expand / collapse

Summary

The Claude Code terminal TUI shows a continuous context-window usage indicator (percent remaining), which makes it easy to know when to run /compact or /clear. The VS Code native extension does not surface this information persistently — users have to run /context on demand to check.

Request

Add a persistent context-usage indicator to the VS Code extension panel, matching the terminal experience. A footer in the prompt box or a status-bar contribution would both work.

Why it matters

Without a visible indicator, it's easy to let a session run past the point where compacting or clearing would have been the right call. Parity with the terminal UI would close a real usability gap for IDE users.

Environment

  • Claude Code VS Code extension v2.1.117
  • VS Code on macOS

extent analysis

TL;DR

Add a persistent context-usage indicator to the VS Code extension panel to match the terminal experience and improve usability.

Guidance

  • Investigate using a status-bar contribution in VS Code to display the context-usage indicator, as this would provide a consistent and non-intrusive way to show the information.
  • Consider adding a footer to the prompt box as an alternative solution, which could also display the context-usage indicator and provide a clear call-to-action for users to run /compact or /clear.
  • Review the VS Code extension API documentation to determine the best approach for implementing a persistent indicator, and ensure that it aligns with the existing terminal TUI experience.
  • Evaluate the trade-offs between displaying the indicator in the status bar versus the prompt box footer, considering factors such as user experience, screen real estate, and visual clutter.

Notes

The implementation details will depend on the specific requirements and constraints of the VS Code extension and its API, so further research and testing may be necessary to determine the best approach.

Recommendation

Apply a workaround by adding a status-bar contribution or prompt box footer to display the context-usage indicator, as this would provide a more consistent and user-friendly experience across the terminal and VS Code extension interfaces.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Surface context-window usage as a persistent indicator in the VS Code extension [1 comments, 2 participants]