Chrome native host crashes on Windows with Bun panic: "Internal assertion failure"
Resolved 💬 3 comments Opened Jan 28, 2026 by achan18 Closed Feb 1, 2026
The Chrome extension fails to connect to Claude Code on Windows. When attempting to reconnect, the tab navigates to
clau.de/chrome/reconnect and immediately closes. Running the native host manually reveals a Bun runtime crash.
Environment
- OS: Windows 10 (10.0.19045.6456)
- Claude Code version: 2.1.22
- Chrome extension: Installed and enabled
Steps to Reproduce
- Install Claude Code on Windows
- Install Claude Chrome extension
- Run /chrome in Claude Code - shows extension is installed
- Try to reconnect from the Chrome extension
- Tab opens to clau.de/chrome/reconnect then immediately closes
Root Cause
Running the native host manually crashes immediately:
& "C:\Users\Austin\.local\bin\claude.exe" --chrome-native-host
Output:
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \\.\pipe\claude-mcp-browser-bridge-Austin
============================================================
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win10_cu
CPU: sse42 avx avx2
Args: "C:\Users\Austin\.local\bin\claude.exe" "--chrome-native-host"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) jsc standalone_executable
Builtins: [...]
Elapsed: 486ms | User: 750ms | Sys: 125ms
RSS: 0.52GB | Peak: 0.52GB | Commit: 0.50GB | Faults: 127491 | Machine: 67.84GB
panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Bun Crash Report
Verified Setup
- Native messaging host is registered in Windows registry ✓
- Manifest file exists at registered path ✓
- Batch file exists and points to correct claude.exe ✓
- claude.exe exists ✓
Expected Behavior
The native host should start successfully and allow the Chrome extension to connect.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗