← ClaudeAtlas

chrome-troubleshooterlisted

Diagnose and fix Claude Chrome extension connectivity issues. Use when browser automation tools fail with "extension not connected" or similar errors.
IgnatRozhkoTR/governed-workflow · ★ 8 · AI & Automation · score 78
Install: claude install-skill IgnatRozhkoTR/governed-workflow
# Chrome Extension Troubleshooter Diagnose Claude Code CLI + Chrome extension connectivity issues. ## When to Use - `mcp__claude-in-chrome__*` tools fail - "Browser extension is not connected" error - Extension shows "Enabled" but tools timeout ## Quick Diagnosis (Run These) ```bash # 1. Can native host execute? ~/.claude/chrome/chrome-native-host --version 2>&1 # 2. Is socket created? ls -la /var/folders/**/claude-mcp-browser-bridge* 2>/dev/null # 3. Is process running? pgrep -fl "chrome-native-host" # 4. What does manifest point to? cat ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json | jq -r .path # 5. Quarantine check xattr ~/.claude/chrome/chrome-native-host ``` ## Failure Mode Decision Tree ``` Tools fail │ ├── Native host --version fails? │ └── Gatekeeper Blockade → Fix: Remove quarantine │ ├── Socket exists but no process? │ └── Zombie Bridge → Fix: Delete socket, restart Chrome │ ├── Manifest path wrong? │ └── Path Rot → Fix: Edit manifest (see docs) │ └── Everything looks OK? └── Service Worker stuck → Fix: Full Chrome restart (Cmd+Q) ``` ## Fixes ### Fix 1: Remove Quarantine (Gatekeeper) ```bash xattr -d com.apple.quarantine ~/.claude/chrome/chrome-native-host chmod +x ~/.claude/chrome/chrome-native-host ``` ### Fix 2: Delete Orphan Socket ```bash rm /var/folders/**/claude-mcp-browser-bridge* 2>/dev/null ``` ### Fix 3: Full Chrome Re