[BUG] Statusline feature regression in VSCode UI updates

Resolved 💬 8 comments Opened Sep 30, 2025 by danieliser 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:

  1. No more stausline, no context meter, no PWD, etc
  2. 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

None

Steps 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_

View original on GitHub ↗

This issue has 8 comments on GitHub. Read the full discussion on GitHub ↗