Chrome native host crashes with Bun panic on Windows
Resolved 💬 3 comments Opened Feb 4, 2026 by oberth-impact Closed Feb 7, 2026
Description
The Chrome native host (claude --chrome-native-host) crashes immediately on startup with a Bun runtime panic on Windows 11.
Environment
- Claude Code version: 2.1.31
- Chrome extension version: 1.0.41
- OS: Windows 11 (x64)
- Bun version: 1.3.5 (1e86cebd)
Steps to Reproduce
- Install Claude Code 2.1.31 on Windows
- Install the Chrome extension (v1.0.41)
- Enable chrome integration with
--chromeflag or/chromecommand - Attempt to connect from Chrome extension
Crash Output
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-rob
============================================================
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win11_ga
CPU: sse42 avx avx2
Args: "C:\Users\rob\.local\bin\claude.exe" "--chrome-native-host"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc standalone_executable
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:querystring" "node:stream" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "node:worker_threads" "undici" "ws" "node-fetch" "node:http2"
Elapsed: 976ms | User: 578ms | Sys: 109ms
RSS: 0.50GB | Peak: 0.50GB | Commit: 0.48GB | Faults: 122888 | Machine: 17.01GB
panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Bun Crash Report Link
Notes
- Reinstalling Claude Code did not fix the issue
- Claude Desktop's Chrome integration works fine (uses separate
chrome-native-host.exebinary, not Bun) - The crash occurs immediately during socket listener creation
- Native messaging host manifest and registry entries are correctly configured
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗