[BUG] Chrome crashes when clicking "Reconnect extension" in `/chrome` menu

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?

Chrome crashes immediately upon selecting "Reconnect extension". The native messaging host binary is never created, leaving the Claude Desktop connector in a permanent "connection failed" state.

What Should Happen?

Reconnect extension should establish the native messaging host connection between Claude Code and the Chrome extension, allowing Claude Desktop to connect to Claude in Chrome.

Error Messages/Logs

# Upon opening Claude desktop:
Could not connect to MCP server mcp-registry
Could not connect to MCP server Claude in Chrome

Steps to Reproduce

1. Install Claude in Chrome extension from Chrome Web Store
2. Open Claude Code and run /chrome
3. Select "Reconnect extension" from the menu
4. Chrome crashes immediately

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.50 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Environment

• macOS Sequoia 15.3
• Google Chrome 145.0.7632.110 (Official Build) (arm64)
• Claude Code 2.1.50
• Claude in Chrome extension 1.0.54

Additional context

• The /chrome status shows "Enabled" and "Extension: Installed" but "Reconnect extension" consistently crashes Chrome
• Manually creating com.anthropic.claude_code_browser_extension.json in ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ does not resolve the issue as the native messaging host binary itself is missing
• find ~/.local -name "*native*" and find ~/.local -name "*messaging*" return no results, confirming the binary was never created
• Claude Desktop shows "Could not connect to MCP server Claude in Chrome" as a result
• No crash logs appear in ~/Library/Logs/DiagnosticReports/ despite Chrome visibly crashing — the crash is silent and generates no diagnostic report