Chrome native messaging host crashes on Windows with Bun panic
Resolved 💬 3 comments Opened Feb 5, 2026 by brandon695 Closed Feb 5, 2026
Description
The Chrome native messaging host crashes immediately on Windows when the browser extension attempts to connect, preventing all browser automation features from working.
Environment
- OS: Windows 11 (MINGW64_NT-10.0-26100)
- Claude CLI Version: Bun v1.3.5 (1e86cebd)
- Chrome Extension ID: fcoeoabgfenejglbffodgkkbkcdhcgfn
Error Output
\
Steps to Reproduce
- Install Claude CLI on Windows 11
- Install Claude Chrome extension from chrome://extensions
- Attempt to use any browser automation feature
- Connection fails with "Browser extension is not connected"
- Test native host directly: 6. Observe crash with Bun panic
Expected Behavior
Native messaging host should initialize successfully and maintain connection with Chrome extension.
Actual Behavior
Native host crashes immediately with internal assertion failure, preventing any browser automation functionality.
Additional Context
- Registry key properly configured at - Manifest file exists at - Native host bat file exists and points to correct claude.exe path
- Multiple reinstalls of CLI, extension, and Chrome did not resolve issue
- Issue appears to be in the Bun runtime within the CLI itself
This blocks all browser automation features on Windows.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗