Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] VS Code `/context` command missing native token usage dialog behavior [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#54174•Fetched 2026-04-29 06:34:18
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeekgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/vs-code

Section/Topic

/context command behavior in VS Code, especially in the prompt box / command menu guidance

Current Documentation

The VS Code page currently says:

  • Command menu: click / or type / to open the command menu. Options include attaching files, switching models, toggling extended thinking, viewing plan usage (/usage), and starting a Remote Control session (/remote-control). The Customize section provides access to MCP servers, hooks, memory, permissions, and plugins. Items with a terminal icon open in the integrated terminal.

  • Context indicator: the prompt box shows how much of Claude's context window you're using. Claude automatically compacts when needed, or you can run /compact manually.

The commands reference currently says:

| /context | Visualize current context usage as a colored grid. Shows optimization suggestions for context-heavy tools, memory bloat, and capacity warnings |

But the changelog for v2.1.121 says:

[VSCode] /context now opens a native token usage dialog

What's Wrong or Missing?

The docs still describe /context with the terminal-style colored-grid behavior and do not explain the VS Code-specific UI change introduced in v2.1.121.

For VS Code users, the main integration page does not mention that /context now opens a native token usage dialog, so the feature is harder to discover from the command menu and harder to recognize when troubleshooting context pressure.

Suggested Improvement

Update the VS Code docs to document the new behavior explicitly:

  1. In vs-code, add /context alongside /usage in the command menu description.
  2. Add a short note near the context indicator explaining that running /context in VS Code opens the native token usage dialog for a more detailed view.
  3. In the commands reference, keep the general /context description but add a VS Code note that this command opens a native token usage dialog there instead of the inline terminal visualization.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/vs-codeVS Code command menu and context indicator bullets omit the /context dialog behavior
https://code.claude.com/docs/en/commands/context is described as a colored grid without a VS Code-specific note
https://code.claude.com/docs/en/errorsTroubleshooting tells users to run /context to inspect context pressure, but does not clarify how this appears in VS Code

Total scope: 3 pages affected

Source: Changelog v2.1.121

Exact changelog entry: [VSCode] /context now opens a native token usage dialog

extent analysis

TL;DR

Update the VS Code documentation to reflect the new behavior of the /context command, which now opens a native token usage dialog.

Guidance

  • Review the affected pages (VS Code command menu, commands reference, and errors troubleshooting) to ensure consistency in documenting the new /context behavior.
  • Add a note to the context indicator section explaining that running /context in VS Code opens the native token usage dialog.
  • Consider adding a VS Code-specific note to the /context description in the commands reference to avoid confusion.
  • Verify that the updated documentation accurately reflects the current behavior of the /context command in VS Code.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The updates should be made to the following pages: https://code.claude.com/docs/en/vs-code, https://code.claude.com/docs/en/commands, and https://code.claude.com/docs/en/errors.

Recommendation

Apply workaround: Update the documentation to reflect the new behavior of the /context command, as this will improve the discoverability and understanding of the feature for VS Code users.

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…
#api#ssr#optimization#dependency conflict#environment setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING