[BUG] `--chrome-native-host` crashes with Bun panic on Windows (v2.1.30)

Resolved 💬 3 comments Opened Feb 3, 2026 by antenando Closed Feb 7, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

claude.exe --chrome-native-host crashes immediately with a Bun internal assertion failure on Windows, preventing the
Chrome extension from connecting. The native host process never stays alive.

What Should Happen?

The Chrome extension should connect successfully to the native host, and claude --chrome should work without crashing.

Error Messages/Logs

[Claude Chrome Native Host] Initializing...
  [Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-FBueno

  Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
  panic(main thread): Internal assertion failure
  Bun has crashed. This indicates a bug in Bun, not your code.

  https://bun.report/1.3.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

Steps to Reproduce

  1. Install Claude Code 2.1.30 via npm install -g @anthropic-ai/claude-code
  2. Install the Claude Chrome extension (v1.0.41)
  3. Run claude --chrome or directly claude.exe --chrome-native-host
  4. Native host crashes instantly

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

N/A

Claude Code Version

2.1.30 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Previously had the Claude Chrome extension working in Brave browser. Then installed Claude Desktop, which may have
modified native messaging host configs. Later uninstalled Claude Desktop and switched to official Chrome. The extension in
Brave stopped working around that time too.

The native messaging host manifest, registry entry, and extension are all correctly configured - the issue is that the
bundled Bun runtime (v1.3.5) panics on startup before the native host can listen for connections.

Bun crash report:
https://bun.report/1.3.5/e_11e86cebEugggC++08F+mvBoxhkf0389e__0shkwCA0eNrzzCtJLcpLzFFILC5OLSrJzM9TSEvMzCktSgUAiSkKPg

## Environment

  • Claude Code version: 2.1.30
  • OS: Windows 11 (build 26100)
  • Architecture: x64 (sse42 avx avx2)
  • Chrome extension: v1.0.41 (fcoeoabgfenejglbffodgkkbkcdhcgfn)
  • Bun (bundled): v1.3.5 (1e86cebd)

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗