[BUG] /terminal-setup doesn't detect VS Code Insiders — installs keybinding to wrong path

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?

/terminal-setup installs the Shift+Enter keybinding to ~/Library/Application Support/Code/User/keybindings.json, which is the regular VS Code path. VS Code Insiders reads from ~/Library/Application Support/Code - Insiders/User/keybindings.json. Shift+Enter doesn't work until the binding is manually copied to the Insiders path.

What Should Happen?

/terminal-setup should detect whether the user is running VS Code or VS Code Insiders and install the keybinding to the correct path.

Error Messages/Logs

Steps to Reproduce

1. Open VS Code Insiders integrated terminal
2. Run claude
3. Run /terminal-setup
4. It reports success and points to the regular Code keybindings.json
5. Press Shift+Enter — nothing happens
6. Manually copy the binding to ~/Library/Application Support/Code - Insiders/User/keybindings.json
7. Reload window — Shift+Enter now works

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.42

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_