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.