Claude-in-Chrome native host crashes on Windows when username contains spaces

Description

The Chrome native host crashes with a Bun runtime panic when the Windows username contains a space. This prevents Claude-in-Chrome from connecting to Claude Code.

Environment

• Claude Code version: 2.1.31
• Chrome extension version: 1.0.44
• OS: Windows 11 (10.0.26200.7628)
• Bun version: 1.3.5

Root Cause

The native host creates a named pipe using the Windows username:

\.\pipe\claude-mcp-browser-bridge-Marcus Gollahon

The space in the username causes Bun to crash with an internal assertion failure.

Crash Output

[Claude Chrome Native Host] Initializing...
[Claude Chrome Native Host] Creating socket listener: \.\pipe\claude-mcp-browser-bridge-Marcus Gollahon
============================================================
Bun v1.3.5 (1e86cebd) Windows x64 (baseline)
Windows v.win11_dt

panic(main thread): Internal assertion failure
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

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

Steps to Reproduce

1. Have a Windows user account with a space in the name (e.g., "Marcus Gollahon")
2. Install Claude Code and Chrome extension
3. Run /chrome or attempt to use Claude-in-Chrome tools
4. Native host crashes, extension cannot connect

Expected Behavior

Named pipe should handle usernames with spaces, either by:

• Quoting/escaping the pipe name
• Replacing spaces with underscores or other safe characters
• Using a hash or UUID instead of the raw username

Workaround

Currently none, other than creating a new Windows user without spaces in the name.