[BUG] Browser extension pipe conflict with Claude Code CLI on Windows - 85+ open issues, needs priority fix

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?

The Chrome browser extension cannot connect to Claude Code CLI on Windows. The error "Browser extension is not connected" appears even though the MCP server shows as "connected".

Root Cause Theory: Claude Code CLI and the browser extension appear to be competing for the same named pipe or IPC channel on Windows. When both try to use the same communication pipe, one blocks the other.

Impact: This is affecting a massive number of users - there are currently 85+ open issues related to this browser connectivity problem on Windows. Issues include #21809, #21952, #21954, #21704, #21211, and many more.

This should be a relatively simple fix - the pipe/IPC naming or allocation just needs to be made unique per session or use separate channels for CLI vs browser extension communication.

Please prioritize this - it's been broken across multiple releases (tested up to v2.1.29) and is a critical feature for Windows users.

What Should Happen?

The browser extension should connect successfully to Claude Code and allow browser automation tools to work. The MCP connection should be stable and not show "Browser extension is not connected" errors.

Error Messages/Logs

Steps to Reproduce

1. Install Claude Code on Windows (v2.1.29 or earlier)
2. Install the Claude in Chrome browser extension
3. Start Claude Code in terminal
4. Try to use any browser automation MCP tool
5. Error appears: "Browser extension is not connected"
6. Check MCP server status - shows "connected" but tools still fail

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.19

Claude Code Version

2.1.29 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_