[Windows] Chrome native host crashes with Bun assertion failure on pipe creation
Resolved 💬 3 comments Opened Feb 8, 2026 by Danielbluz Closed Feb 12, 2026
Description
The Chrome native messaging host (claude.exe --chrome-native-host) crashes immediately on startup with a Bun internal assertion failure when trying to create the named pipe on Windows. This prevents the "Claude in Chrome" extension from connecting to Claude Code.
Environment
- Claude Code version: 2.1.37
- OS: Windows 11 (10.0.26200.7705)
- Bun version: Canary v1.3.9-canary.51 (d5628db2)
- Chrome extension: Claude in Chrome v1.0.47
- Architecture: x64 (baseline), CPU: sse42 avx avx2
Steps to Reproduce
- Install Claude Code v2.1.37 on Windows 11
- Install "Claude in Chrome" extension (v1.0.47) in Chrome
- Open Chrome, activate the extension (Ctrl+E), log into claude.ai
- Extension tries to connect via native messaging - fails silently
Or manually test the native host:
"C:\Users\<user>\.local\bin\claude.exe" --chrome-native-host
Crash Output
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \\.\pipe\claude-mcp-browser-bridge-<username>
============================================================
Bun Canary v1.3.9-canary.51 (d5628db2) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\<user>\.local\bin\claude.exe" "--chrome-native-host"
Features: Bun.stdin(2) jsc standalone_executable
Builtins: "bun:main" "node:buffer" "node:child_process" ...
Elapsed: 109ms | User: 78ms | Sys: 31ms
RSS: 0.29GB | Peak: 0.29GB | Commit: 0.42GB
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
Analysis
- Crash occurs at named pipe creation step (
\\.\pipe\claude-mcp-browser-bridge-<username>) - Process exits with code 3
- 100% reproducible on every invocation
- Native messaging manifests and registry keys are correctly configured
- Extension correctly tries both
com.anthropic.claude_browser_extension(Desktop) andcom.anthropic.claude_code_browser_extension(Code) hosts
Expected Behavior
claude.exe --chrome-native-host should start, create the named pipe, and respond to the extension's ping with a pong, enabling the Claude in Chrome MCP tools.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗