[BUG] CLI and VS Code extension conflict on Windows — extension unusable until CLI is uninstalled

Description

On Windows 11, when both the Claude Code CLI (via npm) and the VS Code extension are installed simultaneously, there is a conflict between them. The user was unable to use the Claude Code VS Code extension normally until the CLI was uninstalled.

Steps to Reproduce

1. Install the Claude Code VS Code extension
2. Install Claude Code CLI globally (via npm)
3. Try to use the extension in VS Code
4. Expected: extension works normally
5. Actual: extension behavior is broken/unresponsive until CLI is removed

Environment

• OS: Windows 11 Home (10.0.26100)
• VS Code extension only (after uninstalling CLI, everything works fine)

Workaround

Uninstall the CLI and use only the VS Code extension.

Notes

This may be related to other conflict reports like #20546 and #22304, which describe CLI/extension conflicts around IPC/named pipes and browser extension connectivity. However this specific case is about the VS Code extension being unusable when the CLI is installed on the same machine.