IDE integration tip references VS Code proprietary shell command — missing in VS Code OSS forks

Summary

Claude Code surfaces the following tip:

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

This tip assumes Microsoft's proprietary VS Code distribution. The command \"Shell Command: Install 'code' command in PATH\" is added by Microsoft and is not present in VS Code OSS builds or any editor forked from VS Code OSS (e.g. Antigravity, VSCodium, Cursor, etc.). Users on those editors open the Command Palette, search for the command, and find nothing — with no indication of what to do instead.

Environment

• OS: Darwin arm64 25.5.0
• Editor: Antigravity 1.23.2 (VSCode OSS 1.107.0, commit 15487b3041e65228cae24980a3f796c905ef582c)
• Claude Code: 2.1.141
• Electron: 39.2.3 / Node.js: 22.21.1
• Language Server CLI: 900566399

Expected behavior

The tip should either:

1. Detect whether the running editor is Microsoft VS Code specifically (vs. a VS Code OSS fork) and suppress or adjust the tip accordingly, or
2. Replace the command-specific instruction with a generic pointer to the IDE integration docs that covers OSS forks and alternative editors.

Actual behavior

The VS Code-proprietary tip fires for all VS Code-based editors regardless of distribution. The referenced Command Palette action does not exist in VS Code OSS forks, leaving the tip with no actionable path for the user.

Notes

The \"Shell Command: Install 'code' command in PATH\" command is documented as a Microsoft VS Code feature. VS Code OSS forks typically ship their own CLI binary under a different name (e.g. antg, codium) and do not include this Command Palette entry. A more robust tip would name the docs URL and note that CLI setup varies by editor.