Chrome native host crashes on Windows - Bun 1.3.5 panic on named pipe creation

Bug Description

The Chrome native host (claude.exe --chrome-native-host) crashes immediately on Windows when attempting to create the named pipe for the browser bridge. This prevents the Claude in Chrome (Beta) feature from working on Windows.

Environment

• Claude Code version: 2.1.29
• OS: Windows 11
• Chrome extension version: 1.0.41
• Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn

Steps to Reproduce

1. Install Claude Code 2.1.29 on Windows
2. Install Claude in Chrome extension
3. Configure native messaging host (registry + JSON config are correct)
4. Attempt to connect via mcp__claude-in-chrome__tabs_context_mcp or run the native host directly

Error Output

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-jfago
============================================================
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2

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__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Root Cause

Claude Code 2.1.29 embeds Bun 1.3.5. The crash occurs during named pipe creation (\.\pipe\claude-mcp-browser-bridge-{user}). The latest Bun release is 1.3.8, which may contain fixes for this Windows named pipe issue.

Additional Context

• Native messaging host config and registry entries are correctly configured
• The Chrome extension itself works fine (connects, shows "Connected" status)
• The crash is in the Bun runtime, not application code
• Claude Desktop's Chrome integration does NOT have this issue (uses a different native host binary)
• Workaround attempted: Disabling Claude Desktop's native messaging host to avoid conflicts — did not resolve the issue since the crash is in Claude Code's own native host process

Expected Behavior

claude.exe --chrome-native-host should start successfully and create the named pipe bridge, allowing the Chrome extension to communicate with Claude Code.