Chrome native host crashes on Windows with Bun 1.3.5 - Internal assertion failure
Resolved 💬 3 comments Opened Jan 28, 2026 by Symple44 Closed Feb 1, 2026
Description
The Chrome native host crashes immediately on Windows when trying to use the /chrome command to connect to the Claude in Chrome extension.
Environment
- OS: Windows 11
- Claude Code version: 2.1.20
- Bun version: 1.3.5
- Chrome extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn (official Claude in Chrome)
Steps to Reproduce
- Install Claude Code on Windows
- Install the Claude in Chrome extension
- Run
claudeand use/chromecommand - Or manually run:
claude.exe --chrome-native-host
Error Output
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-AdminRemote
============================================================
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2 avx512
panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Crash Report
Configuration Files
The native messaging host is correctly configured:
Registry: HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code.chrome_bridge
JSON config (~/.claude/chrome/com.anthropic.claude_code.chrome_bridge.json):
{
"name": "com.anthropic.claude_code.chrome_bridge",
"description": "Claude Code Chrome Bridge",
"path": "C:\Users\...\chrome-native-host.bat",
"type": "stdio",
"allowed_origins": ["chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/"]
}
Expected Behavior
The native host should start successfully and allow communication between Claude Code and the Chrome extension.
Actual Behavior
The native host crashes with a Bun internal assertion failure before any communication can occur.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗