[BUG] Legacy CLI Integration VS Code extension is no longer autoinstalled and hasn't been since v1.0.109
Resolved 💬 4 comments Opened Oct 2, 2025 by ts-shu Closed Jan 8, 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?
https://docs.claude.com/en/docs/claude-code/vs-code#legacy-cli-integration indicates that the legacy vscode cli extension should still be autoinstalled
However, this isn't the case. In fact, claude-code.vsix hasn't been around in the package since 1.0.109
This is particularly confusing because /status still reports something like
IDE: Installed VS Code extension
````
Additionally, https://docs.claude.com/en/docs/claude-code/settings#:~:text=CLAUDE_CODE_IDE_SKIP_AUTO_INSTALL still exists but no longer seems to have any effect on the vscode extension install
### What Should Happen?
The legacy CLI extension should continue to be autoinstalled
### Error Messages/Logs
```shell
Steps to Reproduce
- Uninstall existing installs of the
Claude Code for VS Codeextension - Use any version of claude code > 1.0.109
- See that the extension does not auto install
- check
/statuswhich reports
IDE Integration • /config
✔ Installed VS Code extension
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.0.109
Claude Code Version
1.0.110 -> 2.0.5
Platform
Google Vertex AI
Operating System
Ubuntu/Debian Linux
Terminal/Shell
VS Code integrated terminal
Additional Information
_No response_
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗