[BUG] /context command no longer display in chat window on VS Code ext version 2.1.45
Status Open
Reported on v2.1.45
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 4 comments · opened Feb 18, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When I run the /context command in VS Code extension, it usually depicts a table in the chat window and other structured text about the context window. This no longer works as of about 8:30 pm Pacific time, and it looks like my Claude Code extension auto-updated an hour ago. Version 2.1.45
What Should Happen?
Claude should show stats on context window when I type the /context command and submit to the chat window.
Error Messages/Logs
None. Claude even says they see the output, but I can't.
Steps to Reproduce
- Install Claude Code VS Code extension 2.1.45.
- Open VS Code.
- Open Claude Code window.
- Type /context and submit
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.44
Claude Code Version
2.1.45
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
4 Comments
Same issue appears to affect /cost
Just an FYI for those looking at this bug report, you can ask Claude to print out the system message as a workaround until this is fixed.
All the info is there when you ask Claude to display it, it just doesn't display after the command is issued. (v 2.1.49)
Confirmed.
Step 1: Submit
/contextto a Claude Code chat window.Step 2: Submit a prompt for Claude to print out the results of the last
/contextcall.Doesn't seem to be "hallucinated".
Still not working on Version 2.1.63...
The work around of prompting it via @karimahta suggestion works for the time being.
I believe the response itself consumes tokens, which means whatever it displays to you is "slightly" outdated the moment it is generated. Hopefully this gets addressed.