claude-in-chrome-troubleshooting

Diagnose and fix Claude in Chrome MCP extension connectivity failures on macOS.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/marumo333/atrox --skill claude-in-chrome-troubleshooting-marumo333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-in-chrome-troubleshooting
Source: https://github.com/marumo333/atrox/tree/main/.claude/skills/trailofbits/plugins/claude-in-chrome-troubleshooting/skills/claude-in-chrome-troubleshooting
Command: npx skills add https://github.com/marumo333/atrox --skill claude-in-chrome-troubleshooting-marumo333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Claude in Chrome MCP tools fail with "Browser extension is not connected" or behave erratically because Claude.app (Cowork) and Claude Code CLI register competing native messaging hosts with incompatible socket formats. This Skill diagnoses the conflict and restores the browser bridge connection. ## Core Features & Use Cases - Native Host Conflict Resolution: Identify which native messaging config is active and disable the competing one, since Claude.app and Claude Code cannot run browser automation simultaneously. - Socket and Process Diagnosis: Run shell commands to inspect running native host binaries, socket locations, open files, and TMPDIR configuration. - Full Reset Procedure: Follow a step-by-step reset covering wrapper script updates, stale socket cleanup, Chrome restart, and Claude Code restart. - Use Case: After updating Claude Code, your mcp__claude-in-chrome__ tools suddenly fail. Use this Skill to discover the wrapper script has a hardcoded stale version, replace it with a dynamic version lookup, and restart Chrome and Claude Code. ## Quick Start Diagnose why my Claude in Chrome MCP tools report "Browser extension is not connected" and walk me through the fix.

Frequently Asked Questions about claude-in-chrome-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix "Browser extension is not connected" in Claude Code?▼

The error usually means the wrong native messaging host is active. Disable the Claude.app config (com.anthropic.claude_browser_extension.json) by renaming it with a .disabled suffix, then restart Chrome and Claude Code, since MCP connects only at startup.

Why do Claude.app and Claude Code conflict over Chrome automation?▼

Both register native messaging configs in Chrome but use different native host binaries and incompatible socket formats. When the wrong binary runs, it creates sockets the MCP client cannot find, so only one can be active at a time.

Can I use Cowork and Claude Code CLI browser automation at the same time?▼

No, you cannot use both simultaneously because their native hosts create sockets in different locations and formats. Pick one, disable the other's native messaging config, and use the provided toggle shell function to switch between them.

Does this troubleshooting skill work on Linux or Windows?▼

No, this skill covers macOS-specific paths and tools only, such as ~/Library/Application Support/ and osascript. Linux and Windows users need different diagnostic procedures for their native messaging host configurations.

Why do MCP tools still fail after the native host is running?▼

MCP connects at startup, so if the browser bridge was not ready when Claude Code launched, the session stays broken. Ensure Chrome and the extension are running with the correct config, then restart Claude Code.

How do I fix a stale hardcoded version in the chrome-native-host wrapper?▼

Replace the hardcoded version path in ~/.claude/chrome/chrome-native-host with a dynamic lookup using ls -t on ~/.local/share/claude/versions/ to find the latest binary. This prevents breakage after every Claude Code update.