Claude in Chrome: SSE server not starting on port 22899 (Windows)

## Description
The CLI cannot connect to the Chrome extension. The MCP tools (mcp__claude-in-chrome__*) return "Browser extension
is not connected" even though the extension is installed and working standalone.

## Environment

• OS: Windows 10/11
• Claude Code CLI: 2.1.23
• Chrome Extension: 1.0.41 (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
• Chrome: Latest stable

## Symptoms

1. Chrome extension works fine in sidepanel (can prompt Claude directly in browser)
2. CLI shows mcp__claude-in-chrome__* tools available
3. Any Chrome tool call returns: "Browser extension is not connected"
4. Port 22899 has no listener (netstat -ano | findstr 22899 returns nothing)
5. chrome-native-host.exe process IS running

## Verified Configuration

• Native messaging host manifest exists at:

%LOCALAPPDATA%\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension.json

• Registry key exists at:

HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension

• Bat file exists at: %USERPROFILE%\.claude\chrome\chrome-native-host.bat

## Steps to Reproduce

1. Install Claude Code CLI (2.1.23)
2. Install Claude Chrome extension from Chrome Web Store
3. Run claude in terminal
4. Try any mcp__claude-in-chrome__* tool (e.g., tabs_context_mcp)
5. Observe "Browser extension is not connected" error

## Expected Behavior
SSE server should start on localhost:22899 enabling CLI-to-Chrome communication.

## Actual Behavior
SSE server never starts. Native host process runs but doesn't create the SSE listener.

## Regression
This was working approximately 2-3 days ago. Stopped working without any obvious configuration changes.

## Troubleshooting Attempted

• Restarted Chrome multiple times
• Reinstalled native messaging host manifest
• Re-added registry keys
• Verified extension permissions include nativeMessaging
• Confirmed chrome-native-host.exe is running