Chrome Native Host crashes with Bun panic on Windows 11

Bug Description

The Chrome Native 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.37
• OS: Windows 11
• Bun version (bundled): Canary v1.3.9-canary.51 (d5628db2) Windows x64 (baseline)

Steps to Reproduce

1. Install Claude Code v2.1.37 on Windows 11
2. Install the Claude Chrome extension (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
3. Run claude --chrome-native-host from a terminal

Expected Behavior

The native host should start and create the named pipe for browser bridge communication.

Actual Behavior

The native host crashes with a Bun internal assertion failure when attempting to create the named pipe:

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-jim2m
============================================================
Bun Canary v1.3.9-canary.51 (d5628db2) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\jim2m\.local\bin\claude.exe" "--chrome-native-host"
Features: Bun.stdin(2) jsc standalone_executable
Builtins: "bun:main" "node:buffer" "node:child_process" "node:crypto" "node:fs" "node:fs/promises" "node:net" "node:os" "node:path" "node:process" "node:stream" "node:timers/promises" "node:url" "node:util"
Elapsed: 80ms | User: 15ms | Sys: 46ms
RSS: 0.30GB | Peak: 0.30GB | Commit: 0.42GB | Faults: 73011 | Machine: 68.37GB

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.9/e_2d5628dbEkgggC+s1oU+vvkOu8t/uBysi5uB__qt24tCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Additional Context

• Native Messaging host is correctly registered in the Windows registry
• The manifest at %APPDATA%\Claude Code\ChromeNativeHost\com.anthropic.claude_code_browser_extension.json is correctly configured
• The Chrome extension is installed and enabled with matching extension ID
• The crash occurs at the named pipe creation step (\.\pipe\claude-mcp-browser-bridge-<username>)
• No other Claude processes are running when the crash occurs