claude-in-chrome-troubleshooting

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill claude-in-chrome-troubleshooting-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-in-chrome-troubleshooting
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/claude-in-chrome-troubleshooting
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill claude-in-chrome-troubleshooting-tech-hy

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. - Guided Diagnostics: Run shell commands to inspect running native host binaries, socket locations, open file handles, and active Chrome native messaging configs. - Full Reset Procedure: Update the version-agnostic wrapper script, kill stale native hosts, clean sockets, and restart Chrome and Claude Code in the correct order. - Use Case: After updating Claude Code, your mcp__claude-in-chrome__* tools stop working. Use this Skill to discover the wrapper still points to an old version, apply the dynamic-version wrapper, and restart everything to reconnect. ## 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 in Chrome's NativeMessagingHosts directory, ensure the Claude Code config points to the wrapper, then restart Chrome and Claude Code since MCP connects at startup.

Why do Claude.app and Claude Code browser automation conflict?

Both register native messaging hosts in Chrome but use incompatible socket formats and locations. When the wrong binary runs, the MCP client cannot find its expected socket. You must pick one and disable the other's config; they cannot run simultaneously.

Does this troubleshooting skill work on Linux or Windows?

No. The skill covers macOS-specific paths like ~/Library/Application Support and tools like osascript and getconf DARWIN_USER_TEMP_DIR. Linux and Windows users need different procedures for native messaging host configuration.

Why do Claude in Chrome tools break after updating Claude Code?

The wrapper at ~/.claude/chrome/chrome-native-host may contain a hardcoded version path that becomes stale after updates. Replace it with a dynamic wrapper that resolves the latest version from ~/.local/share/claude/versions/ at runtime.

Can I use the Claude extension in multiple Chrome profiles?

It is not recommended. Each profile with the extension spawns its own native host and socket, causing conflicts. Enable the Claude extension in only one Chrome profile and run only one Claude Code session at a time.