Chrome native messaging host crashes with Bun panic on Windows 11
Resolved 💬 3 comments Opened Feb 13, 2026 by jcarterwil Closed Feb 17, 2026
Description
The Chrome browser extension (claude-in-chrome) never connects on Windows 11. Running claude.exe --chrome-native-host crashes immediately with a Bun runtime assertion failure.
Environment
- OS: Windows 11 Pro 10.0.26200
- Claude Code: 2.1.41
- Chrome Extension: Claude v1.0.49 (ID:
fcoeoabgfenejglbffodgkkbkcdhcgfn) - Chrome Profiles: Extension installed in Profile 1 and Profile 2
Steps to Reproduce
- Install Claude Code 2.1.41 on Windows 11
- Install Claude browser extension v1.0.49 from Chrome Web Store
- Run
/chromein Claude Code — nothing happens in Chrome - All
mcp__claude-in-chrome__*tool calls return "Browser extension is not connected"
Root Cause
Running the native host directly reveals a Bun crash:
> claude.exe --chrome-native-host
[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \\.\pipe\claude-mcp-browser-bridge-CarterWilliams
Bun Canary v1.3.9-canary.62 (6d2fefba) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
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.9/e_26d2fefbEkgggC+s1oU+vvkOu8t/uBysi5uB__qt24tCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg
Verified Configuration (all correct)
- Registry:
HKCU\Software\Google\Chrome\NativeMessagingHosts\com.anthropic.claude_code_browser_extensionpoints to correct JSON config - Native host JSON:
C:\Users\...\AppData\Roaming\Claude Code\ChromeNativeHost\com.anthropic.claude_code_browser_extension.json— correctallowed_originswith matching extension ID - Bat file:
C:\Users\...\.claude\chrome\chrome-native-host.batexists and callsclaude.exe --chrome-native-host - claude.exe: Exists at expected path, runs correctly for all other operations
- Named pipe:
claude-mcp-browser-bridge-{username}gets created but process dies immediately
The native host process creates the named pipe, then crashes before it can accept connections from Chrome. This has persisted across multiple Chrome restarts and Claude Code sessions.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗