[BUG] Statusline feature regression in VSCode UI updates
Status Closed — not planned
Maintainer reply None cached
Activity 8 comments · opened Sep 30, 2025 · closed Jan 7, 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?
The current v2 VS Code integration is huge improvement, but it broke 2 crucial things:
- No more stausline, no context meter, no PWD, etc
- Can't designate which folder claude should run in. Previously you could ctrl+c and just cd to a different folder, granted this is just terminal in a tab, but something we used regularly and now will actually have to use terminals.
The lack of statusline and the details it brought to the table makes me seriously think I'll either be reverting which I hate to do, or using the terminal instead.
What Should Happen?
I should still see status line output and be able to choose a path it runs in (like you can with Python runtimes).
Error Messages/Logs
NoneSteps to Reproduce
None
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
latest
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Cursor
Additional Information
_No response_
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
+1
+1
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.
Love to see the status line in VSCode UI. Being able to see the model, branch name, working dir. are extremely helpful.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
why no statusline in vscode extension? :(
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.