Chrome native host crashes on Windows - Bun internal assertion failure
Resolved 💬 3 comments Opened Feb 3, 2026 by kosardavid Closed Feb 6, 2026
Bug Description
claude --chrome-native-host crashes immediately on startup with a Bun internal assertion failure. The Chrome extension cannot communicate with Claude CLI because the named pipe process dies.
Environment
- Claude Code version: 2.1.29
- OS: Windows 11
- Bun: v1.3.5
Steps to Reproduce
- Install Claude Chrome extension
- Run
claude --chrome-native-host - Process creates pipe
\.\pipe\claude-mcp-browser-bridge-<user>then crashes
Error Output
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-sbor
panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Crash report: https://bun.report/1.3.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg
Additional Context
- The native host
.batwrapper exists at~/.claude/chrome/chrome-native-host.bat - No native messaging host registry entries exist in
HKCUorHKLM - Chrome is running and the extension is installed and enabled
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗