Chrome extension native host crashes on Windows - Bun socket listener panic

Description
The Chrome extension native host crashes immediately on startup on Windows, making it impossible to connect Claude Code CLI to the Chrome extension.

Running claude.exe --chrome-native-host produces a Bun runtime panic:

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

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

Stack Trace

• MiniEventLoop.zig:320 → platformEventLoop
• Listener.zig:115 → listen
• 2 unknown/js code
• llint_entry

The crash occurs in Bun's socket listener when attempting to create the named pipe for communication with the Chrome extension.

Crash Report
https://bun.report/1.3.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Environment

• OS: Windows 11 (x86_64)
• Claude Code CLI: v2.1.32
• Chrome Extension: v1.0.51
• Embedded Bun: v1.3.5
• Latest Bun release: v1.3.9

Root Cause
The embedded Bun v1.3.5 has a bug in the Windows socket listener (Listener.zig:115). The latest stable Bun (v1.3.9) likely includes a fix. Updating the embedded Bun version in Claude Code should resolve this
issue.

Steps to Reproduce

1. Install Claude Code v2.1.32 on Windows 11
2. Install the Claude Chrome extension v1.0.51
3. Run claude.exe --chrome-native-host in a terminal
4. Observe the Bun panic crash

Expected Behavior
The native host should start successfully and establish a named pipe for communication with the Chrome extension.