/chrome integration: chrome-native-host crashes with Internal assertion failure on Windows
Resolved 💬 3 comments Opened Mar 15, 2026 by gangarux Closed Mar 18, 2026
Description
The Claude in Chrome integration (/chrome) always shows "disabled" because the native host process crashes immediately on startup with Internal assertion failure in Bun runtime.
Environment
- Claude Code: 2.1.76
- OS: Windows 11 Pro 10.0.26100
- Installation: native build and npm — same result
- Bun: v1.3.11 (a2743b6d)
Steps to reproduce
- Run:
claude --chrome-native-host - Process crashes immediately
Error output
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.pipeclaude-mcp-browser-bridge-User
panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Crash report
Additional notes
Registry key HKCUSoftwareGoogleChromeNativeMessagingHostscom.anthropic.claude_code_browser_extension is present and points to the correct .bat file. Chrome extension is installed and enabled. The crash occurs before any connection is established.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗