Chrome native messaging host crashes on startup (Bun panic)

Description

The Chrome native messaging host crashes immediately on startup with a Bun internal assertion failure, preventing the Claude in Chrome extension from connecting to Claude Code.

Environment

• Claude Code version: 2.1.22
• OS: Windows 11
• Bun version: 1.3.5

Steps to Reproduce

1. Install Claude Code 2.1.22 on Windows
2. Install the Claude in Chrome extension (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
3. Try to use browser automation tools via mcp__claude-in-chrome__tabs_context_mcp
4. Connection fails with "Browser extension is not connected"

Debug Information

Running the native host directly shows the crash:

$ claude.exe --chrome-native-host

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-ChawanusBoonyavanich

panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Bun Crash Report

https://bun.report/1.3.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzM9TSEvMzCktSgUAiSkKPg

Configuration Verified

All configuration is correct:

• Registry entry exists at HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension
• Native messaging manifest JSON is properly configured
• chrome-native-host.bat wrapper script exists and points to correct claude.exe
• Chrome extension ID matches the allowed_origins in the manifest
• claudeInChromeDefaultEnabled: true in settings

Expected Behavior

The native messaging host should start successfully and create the socket for the Chrome extension to connect.

Actual Behavior

The native messaging host crashes with a Bun internal assertion failure before the socket can be created.