Chrome extension: Bun panics on Windows when creating named pipe for native host

Resolved 💬 4 comments Opened Feb 7, 2026 by corrinebean Closed Mar 10, 2026

Bug Description

The Chrome native host crashes immediately on startup with a Bun internal assertion failure when attempting to create a Windows named pipe socket. This prevents the Claude in Chrome extension from ever connecting to Claude Code.

Steps to Reproduce

  1. Install Claude Code v2.1.37 on Windows 11
  2. Install Claude in Chrome extension (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
  3. Run claude.exe --chrome-native-host from Command Prompt
  4. Observe crash

Error Output

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-corri
================================================================
Bun Canary v1.3.9-canary.51 (d5628db2) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Args: "C:\Users\corri\.local\bin\claude.exe" "--chrome-native-host"
Features: Bun.stdin(2) jsc standalone_executable
Builtins: "bun:main" "node:buffer" "node:child_process" "node:crypto" "node:fs" "node:fs/promises" "node:net" "node:os"
  "node:path" "node:process" "node:stream" "node:timers/promises" "node:url" "node:util"
Elapsed: 71ms | User: 15ms | Sys: 46ms
RSS: 0.30GB | Peak: 0.30GB | Commit: 0.42GB | Faults: 72932 | Machine: 34.19GB

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

Debug Log

From ~/.claude/debug/:

[Claude in Chrome] Adding socket to pool: C:\Users\corri\AppData\Local\Temp\claude-mcp-browser-bridge-corri
[Claude in Chrome] Adding socket to pool: /tmp/claude-mcp-browser-bridge-corri
[Claude in Chrome] Attempting to connect to: C:\Users\corri\AppData\Local\Temp\claude-mcp-browser-bridge-corri
[Claude in Chrome] Socket error (code: ENOENT)
[Claude in Chrome] No connected sockets in pool

Environment

  • OS: Windows 11 (build 26100.7623)
  • Claude Code: v2.1.37
  • Bun: Canary v1.3.9-canary.51 (d5628db2) x64 baseline
  • Chrome extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
  • Native host config: C:\Users\corri\AppData\Roaming\Claude Code\ChromeNativeHost\com.anthropic.claude_code_browser_extension.json

Additional Context

  • The native messaging host registry entry and JSON config are both correct
  • The extension ID matches the allowed_origins in the native host config
  • The crash occurs specifically when Bun tries to create the named pipe at \.\pipe\claude-mcp-browser-bridge-corri
  • Possibly related to #23218 (Windows named pipe discovery issues)

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗