/chrome command produces no output and doesn't connect to Chrome extension

Description

Running /chrome (or starting with claude --chrome) shows the "Claude in Chrome (Beta)" confirmation prompt, but after pressing Enter, nothing happens. No browser tools become available and no error is shown.

Environment

• Claude Code version: 2.1.37
• Chrome extension version: 1.0.41
• OS: macOS (Darwin 25.2.0)
• Plan: Active claude.ai subscription

Steps to Reproduce

1. Start Claude Code with claude --chrome
2. Run /chrome
3. See the "Claude in Chrome (Beta)" prompt with "Enter to confirm / Esc to cancel"
4. Press Enter
5. Nothing happens - no output, no error, no browser tools available

What I've Verified

• Chrome is open and running
• Claude in Chrome extension is installed, enabled, and version 1.0.41
• Native messaging host file exists at ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json (created Dec 20, 2025)
• The native host binary exists at /Applications/Claude.app/Contents/Helpers/chrome-native-host
• claude mcp list shows other MCP servers connected fine (gmail, slack, github, etc.) but no Chrome/browser MCP
• ToolSearch finds no browser/Chrome-related tools available

Debug Log Observations

• Previous sessions (Jan 25, Feb 3, Feb 4) show successful Chrome extension detection:

``
[Claude in Chrome] Found chrome profiles: Profile 29, Profile 16, Profile 32, Profile 35, Default, Profile 39, Profile 38, Profile 36, Profile 31
[Claude in Chrome] Extension fcoeoabgfenejglbffodgkkbkcdhcgfn found in chrome Profile 35
``

• Current session (started Feb 7 with --chrome flag) has zero Chrome-related debug entries despite running /chrome multiple times
• Recurring error in logs: ENOENT: no such file or directory, open '/Users/JJ/.claude/remote-settings.json' (fires every hour)
• Occasional: Failed to save config with lock: Error: Lock file is already being held

Expected Behavior

After pressing Enter on the /chrome prompt, browser automation tools should become available (navigate, click, type, screenshot, etc.).

Actual Behavior

Nothing happens. No tools loaded, no error message, no debug output.