Chrome native host crashes with Bun assertion failure on Windows (--chrome-native-host)

Description

claude.exe --chrome-native-host crashes immediately with a Bun runtime internal assertion failure on Windows 11, preventing the Claude in Chrome extension from connecting to Claude Code.

The Chrome extension discovers and launches the native host, but the process panics before completing the ping/pong handshake, so the connection always fails with "Browser extension is not connected."

Environment

• Claude Code version: 2.1.30
• Chrome extension version: 1.0.41
• OS: Windows 11 (Build 10.0.26200.7623)
• Bun version (bundled): 1.3.5

Steps to reproduce

1. Install Claude Code CLI and Claude in Chrome extension
2. Verify native host registration exists: reg query "HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension"
3. Run: echo '{"type":"ping"}' | claude.exe --chrome-native-host
4. Process crashes instead of responding with {"type":"pong"}

Crash output

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

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

Bun crash report URL: https://bun.report/1.3.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Investigation details

• The Chrome extension correctly tries both native hosts in order: com.anthropic.claude_browser_extension (Desktop) then com.anthropic.claude_code_browser_extension (Code)
• The extension sends a ping message and expects a pong response to confirm the connection
• The native host batch file (chrome-native-host.bat) correctly calls claude.exe --chrome-native-host
• The process starts, creates the named pipe \.\pipe\claude-mcp-browser-bridge-<username>, then crashes
• The Desktop native host (chrome-native-host.exe) works fine — it's a standalone exe, not Bun-based
• Registry entries, manifest JSON, and file paths are all correct

Expected behavior

claude.exe --chrome-native-host should start, respond to the ping/pong handshake, and maintain a connection for browser automation via MCP tools.

Workaround

The extension works with Claude Desktop (which uses its own standalone chrome-native-host.exe). There is no workaround for Claude Code CLI.