claude-in-chrome-troubleshooting

Diagnose and resolve native messaging host conflicts between Claude.app and Claude Code CLI on macOS.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill claude-in-chrome-troubleshooting-manuelbrandner85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-in-chrome-troubleshooting
Source: https://github.com/manuelbrandner85/Weltenbibliothekapp/tree/main/.agents/skills/claude-in-chrome-troubleshooting
Command: npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill claude-in-chrome-troubleshooting-manuelbrandner85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves connectivity failures between the Claude Code CLI and the Claude in Chrome MCP extension, specifically addressing the "Browser extension is not connected" error caused by conflicting native messaging hosts.

Core Features & Use Cases

  • Conflict Resolution: Automatically detects and toggles between Claude.app (Cowork) and Claude Code CLI native messaging configurations.
  • Diagnostic Tools: Provides a suite of commands to verify socket locations, binary paths, and active native messaging configs.
  • Use Case: Use this when you have recently updated your Claude environment or switched between using the Claude Desktop app and the CLI, and your browser automation tools have stopped responding.

Quick Start

Run the chrome-mcp-toggle command in your terminal to switch your native messaging configuration to the correct environment.

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 extension say it is not connected on macOS?

The "Browser extension is not connected" error occurs on macOS due to conflicting native messaging hosts between the Claude.app and Claude Code CLI environments, which disrupt MCP browser automation communication.

How do I fix MCP browser automation when it fails to communicate with the Chrome extension?

To fix MCP browser automation communication, run the shell-based diagnostic scripts to verify socket locations and binary paths, then execute the chrome-mcp-toggle command to switch your native messaging configuration.

What causes native messaging host conflicts between Claude.app and Claude Code CLI?

Native messaging host conflicts happen when switching between the Claude Desktop app and the CLI or after updating your Claude environment, causing configuration mismatches that break Chrome browser extension connectivity.

Do I need to run manual shell commands to restore Claude MCP browser extension connectivity?

Yes, restoring browser extension connectivity requires manual execution of shell-based diagnostic and configuration-toggling scripts on macOS to resolve the underlying native messaging host socket and configuration mismatches.

How do I check my active native messaging configuration for the Claude Chrome extension?

You can check your active native messaging configuration by running the provided diagnostic tools, which verify socket locations, binary paths, and active native messaging configs to identify the source of the connectivity failure.

Can I use this troubleshooting process if I recently updated my Claude environment on macOS?

Yes, this process specifically targets macOS systems where browser automation tools have stopped responding after a recent Claude environment update or after switching between the Claude Desktop app and the CLI.