[BUG] CLI fails to start in Google Antigravity: "Error installing VS Code extension" loop despite manual install

[Flashtendo]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• 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

1. Install Claude Code using the Native Installer on Windows.
2. Use Google Antigravity where the code command is not globally registered or named differently.
3. Manually install the anthropic.claude-code extension via the Marketplace/VSIX.
4. 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

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] VS Code extension auto-install fails when VS Code is not installed #17484
2. [BUG] VSCode integrated terminal cannot detect 'code' command - IDE connection fails (Windows) #13447
3. [Feature Request] Support VSCode Insiders command detection and prefer code-insiders when running #16186

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[Flashtendo]

This is not strictly a duplicate of #17484. The documentation states that manually installing the extension should stop this error, but I have manually installed the extension with the Marketplace and the Native Installer CLI still forces the code check.

[dongzhenye]

Same issue on macOS (Antigravity IDE). The CLI doesn't crash like on Windows, but it shows this tip on every session:

Tip: Open the Command Palette (Cmd+Shift+P) and run "Shell Command: Install 'code' command in PATH" to enable IDE integration

The code binary doesn't exist because Antigravity uses agy / antigravity as its CLI command. Creating a symlink (ln -s agy /usr/local/bin/code) would suppress the tip but risks conflicting with an actual VS Code install.

The root cause is the same: Claude Code hardcodes the code command instead of detecting the actual IDE fork. This affects all VS Code forks (Antigravity, Cursor, Windsurf, VSCodium, etc.).

Suggested fix: Detect the running IDE process or allow users to configure the IDE command in Claude Code settings (e.g., ide.command: "agy").

• Claude Code version: 2.1.45
• macOS Darwin 25.2.0
• Antigravity IDE

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

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.