[BUG] CLI fails to start in Google Antigravity: "Error installing VS Code extension" loop despite manual install
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?
I am using the Native Installer version of Claude Code on Windows with Google Antigravity. Even though I have manually installed the extension from the Marketplace and it is fully active, the claude CLI refuses to recognize that I have installed the extension.
It appears the CLI attempts to verify or enforce the extension installation by executing the standard code command. Since I am on a fork, the code command is not in the system PATH. This results in an "Exit Code 1" crash, blocking access to the tool entirely, even though the environment is actually ready.
What Should Happen?
The CLI should detect that the extension is already installed/running (or allow a manual override) and start normally, instead of failing because it cannot find the specific code binary.
Error Messages/Logs
IDE: X Error installing VS Code extension: 1: Command failed with exit code 1: code --force --install-extension anthropic.claude-code
The command "code" is either misspelled or could not be found.
Please restart your IDE and try again.
Steps to Reproduce
- Install Claude Code using the Native Installer on Windows.
- Use Google Antigravity where the code command is not globally registered or named differently.
- Manually install the anthropic.claude-code extension via the Marketplace/VSIX.
- Open the integrated terminal in the IDE.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.29
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
VS Code integrated terminal
Additional Information
<img width="801" height="74" alt="Image" src="https://github.com/user-attachments/assets/133eedc6-8f42-41a0-877c-bd017a3479ca" />
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗