Chrome native host crashes with Bun internal assertion failure on Windows

Description

The Chrome native host mode (claude --chrome-native-host) crashes immediately on startup with a Bun internal assertion failure. This prevents the Chrome browser extension from connecting to Claude Code.

Environment

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

Error Output

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-user
============================================================
Bun v1.3.5 (1e86cebd) 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.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Steps to Reproduce

1. Run claude --chrome-native-host on Windows
2. Observe crash

Additional Context

• The Chrome extension (v1.0.41) is properly installed
• Registry entries for native messaging host are correct
• The native host manifest file is valid
• This worked previously (last successful connection was January 23, 2026)

Expected Behavior

The native host should start successfully and allow the Chrome extension to connect.