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.