debug-chrome-extension

Diagnose and repair Claude Code Chrome extension connectivity issues across components.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/az9713/my-agent-skills --skill debug-chrome-extension
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-chrome-extension
Source: https://github.com/az9713/my-agent-skills/tree/main/.claude/skills/debug-chrome-extension
Command: npx skills add https://github.com/az9713/my-agent-skills --skill debug-chrome-extension

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix Claude Code Chrome extension connectivity issues when the extension shows Status: Disabled, MCP tools are unavailable, or browser automation fails to connect.

Core Features & Use Cases

  • Diagnose the three-component architecture (Chrome Extension, Native Host, MCP Server, and CLI) and identify where the connection is broken.
  • Provide a step-by-step remediation guide, including verification of processes, named pipes, logs, extension installation, and registry manifests.
  • Offer a full reset procedure to restore a healthy Claude Code Chrome integration in noisy environments.

Quick Start

Open Claude extension in Chrome and click its icon to spawn the native host, then restart Claude Code with claude --chrome.

Frequently Asked Questions about debug-chrome-extension

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

FAQPage Schema
Why does my Claude Chrome extension show Status: Disabled and fail to connect?

A disabled Claude Chrome extension status indicates a broken connection across the Chrome extension, native host, MCP server, or CLI. Diagnosing this three-component architecture identifies exactly where the connectivity failure occurs to restore automation.

How do I fix MCP tools being unavailable in my Claude Code Chrome extension?

To fix unavailable MCP tools, you must diagnose the native host and MCP server connectivity. This involves verifying active processes, checking named pipes, and inspecting logs to identify the broken link between the browser and CLI.

What is the best way to reset the Claude Code Chrome integration when browser automation fails?

The best way to restore a failing Claude Code Chrome integration is a full reset procedure. This remediation clears noisy environment states by reinstalling the extension, verifying registry manifests, and restarting the CLI.

Can I use the Claude Code CLI to troubleshoot Chrome extension native host issues?

Yes, you can troubleshoot native host issues by opening the Claude extension in Chrome to spawn the native host, then restarting Claude Code with the command 'claude --chrome'. This verifies process spawning and re-establishes the connection.

What should I check when the Claude Code browser automation connection breaks?

When the browser automation connection breaks, check the status of the Chrome extension, verify native host processes, inspect named pipes, and review logs. Identifying the failed component in the three-part architecture is essential for repair.