claude-in-chrome-troubleshooting
Diagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", or behave erratically.
Security Assessment
Detected risks:
About claude-in-chrome-troubleshooting
The claude-in-chrome-troubleshooting skill helps diagnose and resolve connectivity and reliability problems between Claude in Chrome MCP tools and the Chrome browser extension environment. It is specifically designed for situations where browser automation tools fail with errors such as "Browser extension is not connected," behave unpredictably, or stop functioning after updates to Claude Code or Claude.app. The skill focuses on identifying conflicts between competing native messaging hosts used by Claude.app and Claude Code CLI on macOS systems, helping users restore stable communication between the browser extension and the MCP client.
The skill provides guidance for troubleshooting native host conflicts, verifying Chrome NativeMessagingHosts configurations, and understanding differences between the socket formats used by Claude.app and Claude Code CLI. It explains how conflicting native messaging configurations can cause MCP connection failures even when processes appear active. The documentation includes practical shell commands for disabling one native host configuration, enabling the correct one, and switching environments depending on whether the user prefers Claude Code CLI or Claude.app Cowork functionality. It also includes a toggle script example for streamlining transitions between the two automation environments.
This skill is intended primarily for macOS users who use browser automation through Claude Code CLI or Claude.app Cowork and encounter extension connectivity issues. It is especially useful for developers, technical users, and automation workflows that depend on reliable Chrome MCP integration. The skill is not intended for Linux or Windows users, general Chrome automation debugging, network troubleshooting, or browser extension installation support. Instead, it targets a very specific interoperability issue involving Chrome native messaging hosts and browser automation tooling.
FAQ
When should I use this skill?
Use this skill when Claude in Chrome MCP tools fail with errors such as "Browser extension is not connected," when browser automation behaves erratically, or after updating Claude Code or Claude.app.
Does this skill support Linux or Windows?
No. The troubleshooting steps are designed specifically for macOS and rely on macOS-specific paths and tools such as ~/Library/Application Support/ and osascript.
Can I use Claude.app Cowork and Claude Code CLI browser automation at the same time?
No. The documentation explains that both systems use competing native messaging hosts and socket formats. One configuration must be disabled while the other is active.
What is the primary issue this skill helps resolve?
The main issue is a conflict between native messaging host configurations registered by Claude.app and Claude Code CLI, which can cause Chrome MCP tools to lose connectivity even though related processes appear to be running.
Does this skill help with general Chrome extension installation problems?
No. The skill is focused on MCP extension connectivity and native host conflicts, not installation or Chrome Web Store support issues.
Install claude-in-chrome-troubleshooting
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
trailofbits/skills