Chrome native messaging host crashes on Windows 11 — Bun 1.3.10 panic

Description

The Chrome native messaging host (claude.exe --chrome-native-host) crashes immediately on startup with a Bun internal assertion failure. This makes the "Claude in Chrome" browser automation completely non-functional on Windows.

Environment

• Claude Code: v2.1.50
• Chrome Extension: v1.0.54 (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
• OS: Windows 11 Pro 10.0.26100
• Bun: v1.3.10 (bundled with Claude Code)
• Chrome: latest stable

Steps to Reproduce

1. Install Claude Code v2.1.50 on Windows 11
2. Install Claude Chrome extension v1.0.54
3. Start Claude Code with claude --chrome
4. Any mcp__claude-in-chrome__* tool call returns "Browser extension is not connected"
5. In Chrome extension Service Worker console, run:

chrome.runtime.connectNative("com.anthropic.claude_code_browser_extension")
Result: Unchecked runtime.lastError: Native host has exited.

Crash Output

Running the native host directly:

$ claude.exe --chrome-native-host

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-<username>
Bun v1.3.10 (1423d3c8) Windows x64 (baseline)

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.10/e_11423d3cEkgggC+hhpU+s7lOop0ivB07t8uB__q9qxtCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Diagnostics

• Registry entries for native messaging hosts: ✅ correct
• chrome-native-host.bat path: ✅ exists, points to correct claude.exe
• claude.exe binary: ✅ exists at ~/.local/bin/claude.exe
• Extension nativeMessaging permission: ✅ present in manifest
• Named pipe \.\pipe\claude-mcp-browser-bridge-<username>: ❌ never created (process crashes before)

Expected Behavior

The native messaging host should stay alive and create the named pipe for communication between Chrome and Claude Code.