chrome-mcp-troubleshooting — Claude Code skill: how to install
Troubleshoots native host clashes between Claude Code and Chrome on macOS. Fixes broken bridge connections when browser tools refuse to run.
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a claude-codeWhat chrome-mcp-troubleshooting does
This skill resolves integration failures between the browser extension and the terminal agent. The root dilemma stems from two competing native hosts on macOS. When Claude.app Cowork is installed alongside Claude Code, both register native messaging definitions in Chrome. The browser picks the wrong binary, creating socket files in an unexpected location. The CLI agent fails to locate the pipe and aborts automation calls.
Inside you will find diagnosis commands targeting Darwin temporary paths, running processes, and active JSON manifests. The guide outlines how to rename the conflicting desktop host configuration and supplies a shell function to toggle between Cowork and CLI modes. It also includes an orderly reset workflow using osascript and process termination.
Because this playbook depends on paths like ~/Library/Application Support/, it is completely ineffective on Windows or Linux machines. Another strict detail matters: MCP client connections happen only during startup. You must launch and configure Chrome before starting the Claude Code session.
What it helps with
- Resolve native messaging host conflicts between Claude.app and Claude Code
- Clear stale socket files in Darwin temporary folders
- Switch Chrome native messaging configs with a shell helper
- Fix disconnected browser MCP tools after application updates
Example prompts for the agent
- Diagnose why mcp__claude-in-chrome reports that the browser extension is disconnected
- Check which native messaging host is active for my Chrome Claude extension
- Help me toggle the Chrome native host from Claude.app to Claude Code CLI
How to install chrome-mcp-troubleshooting
1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a claude-code2Manually: put the files in place
~/.claude/skills/chrome-mcp-troubleshooting/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/chrome-mcp-troubleshooting/
1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a codex2Manually: put the files in place
.agents/skills/chrome-mcp-troubleshooting/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a cursor2Manually: put the files in place
.cursor/skills/chrome-mcp-troubleshooting/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install trailofbits/skills chrome-mcp-troubleshooting2Manually: put the files in place
.github/skills/chrome-mcp-troubleshooting/SKILL.md1Skills CLI (Vercel)
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a gemini-cli2Platform CLI
gemini skills install https://github.com/trailofbits/skills --path plugins/chrome-mcp-troubleshooting/skills/chrome-mcp-troubleshootingManually: put the files in place
.devin/skills/chrome-mcp-troubleshooting/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about chrome-mcp-troubleshooting
How to install chrome-mcp-troubleshooting in Claude Code?
Run npx skills add trailofbits/skills --skill chrome-mcp-troubleshooting -a claude-code in your terminal.
What causes the Claude in Chrome connection error?
Both Claude.app and Claude Code register native messaging configs in Chrome, causing the browser to spawn the wrong host binary and mismatched socket paths.
Does chrome-mcp-troubleshooting support Windows or Linux?
No, the instructions and scripts rely strictly on macOS filesystem locations and utilities such as osascript.