claude-in-chrome-troubleshooting

Diagnose and resolve conflicting native messaging hosts for Claude in Chrome MCP tools.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/ofelixdev/cc-kit --skill claude-in-chrome-troubleshooting-ofelixdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-in-chrome-troubleshooting
Source: https://github.com/ofelixdev/cc-kit/tree/main/template/skills/claude-in-chrome-troubleshooting
Command: npx skills add https://github.com/ofelixdev/cc-kit --skill claude-in-chrome-troubleshooting-ofelixdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps diagnose and resolve connectivity problems between the Claude Code CLI and the Claude in Chrome browser extension, specifically when MCP tools report "Browser extension is not connected" or behave erratically.

Core Features & Use Cases

  • Conflict Resolution: Addresses the primary issue of conflicting native messaging hosts between Claude.app (Cowork) and Claude Code CLI.
  • Configuration Toggling: Provides clear instructions and a script to disable the native host configuration for either Claude.app or Claude Code, allowing only one to be active.
  • Diagnostic Tools: Includes commands to quickly check running processes, socket locations, and active native messaging configurations.
  • Use Case: You're using Claude Code CLI for browser automation, but the mcp__claude-in-chrome__* tools are failing with a connection error. This skill guides you through disabling the Claude.app native host and restarting your applications to re-establish the connection.

Quick Start

Run the chrome-mcp-toggle command in your terminal to switch between Claude Code CLI and Claude.app configurations, then restart Chrome and Claude Code.

Frequently Asked Questions about claude-in-chrome-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does the Claude in Chrome MCP tool report "Browser extension is not connected"?

The "Browser extension is not connected" error occurs when there are conflicting native messaging host configurations between the Claude.app and Claude Code CLI competing for the same socket path on macOS.

How do I fix Claude in Chrome connection issues on macOS?

To fix Claude in Chrome connection issues, run the `chrome-mcp-toggle` script to disable the conflicting native host configuration, then restart Chrome and Claude Code to re-establish the MCP connection.

How do conflicting native messaging hosts affect Claude Code CLI browser automation?

Conflicting native messaging hosts cause erratic behavior because Claude.app and Claude Code CLI compete for the native host binary, resulting in failed MCP tool execution and dropped socket connections.

Can I use Claude.app and Claude Code CLI browser automation simultaneously on macOS?

No, you cannot run both simultaneously because they share native messaging host binaries. You must toggle the active configuration to allow only one application to control the Chrome extension at a time.

What diagnostic commands check native host configurations for Claude in Chrome?

Diagnostic commands check running processes, socket locations, and active native messaging configurations to identify which application, Claude.app or Claude Code CLI, currently holds the native host binary.

How do I disable the Claude.app native host for Chrome MCP tools?

To disable the Claude.app native host, run the provided `chrome-mcp-toggle` command in your terminal to switch configurations, clearing the socket path for Claude Code CLI browser automation.