Chrome native messaging host crashes on Windows (Bun panic - Internal assertion failure)
Resolved 💬 3 comments Opened Feb 6, 2026 by vivimisswed Closed Feb 9, 2026
Bug: Chrome native messaging host crashes on Windows (Bun panic)
Environment
- Claude Code: v2.1.33
- OS: Windows 11
- Chrome: latest
- Extension: Claude in Chrome v1.0.45 (ID: fcoeoabgfenejglbffodgkkbkcdhcgfn)
Description
claude.exe --chrome-native-host crashes immediately with a Bun internal assertion failure. This prevents the Chrome extension from connecting to Claude Code via claude --chrome.
Steps to Reproduce
- Install Claude Code v2.1.33 on Windows 11
- Install "Claude in Chrome" extension
- Run
claude --chrome - Attempt any Chrome MCP tool → "Browser extension is not connected"
Crash Log
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-<user>
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Crash Report URL
Notes
- All configuration files are correct (native messaging host JSON, registry entries, bat file)
claude install --forcedoes not fix the issue (same version reinstalled)- Previously worked, stopped working (likely after an update)
- Native messaging host config at:
%APPDATA%\Claude Code\ChromeNativeHost\com.anthropic.claude_code_browser_extension.json - Registry key exists at:
HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extension
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗