Claude in Chrome MCP Troubleshooting

Chrome中Claude MCP故障排查

Use this skill when Claude in Chrome MCP tools fail to connect or work unreliably.

当Chrome中的Claude MCP工具无法连接或运行不稳定时，使用本技能。

When to Use

适用场景

```
mcp__claude-in-chrome__*
```
tools fail with "Browser extension is not connected"
Browser automation works erratically or times out
After updating Claude Code or Claude.app
When switching between Claude Code CLI and Claude.app (Cowork)
Native host process is running but MCP tools still fail

```
mcp__claude-in-chrome__*
```
工具提示"Browser extension is not connected"并失败
浏览器自动化运行异常或超时
更新Claude Code或Claude.app之后
在Claude Code CLI与Claude.app（Cowork）之间切换时
原生主机进程正在运行，但MCP工具仍无法正常工作

When NOT to Use

不适用场景

Linux or Windows users - This skill covers macOS-specific paths and tools (
```
~/Library/Application Support/
```
,
```
osascript
```
)
General Chrome automation issues unrelated to the Claude extension
Claude.app desktop issues (not browser-related)
Network connectivity problems
Chrome extension installation issues (use Chrome Web Store support)

Linux或Windows用户 - 本技能仅覆盖macOS特定路径与工具（
```
~/Library/Application Support/
```
、
```
osascript
```
）
与Claude扩展无关的通用Chrome自动化问题
Claude.app桌面端问题（非浏览器相关）
网络连接问题
Chrome扩展安装问题（请使用Chrome应用商店支持）

The Claude.app vs Claude Code Conflict (Primary Issue)

Claude.app与Claude Code的冲突（核心问题）

Background: When Claude.app added Cowork support (browser automation from the desktop app), it introduced a competing native messaging host that conflicts with Claude Code CLI.

背景： 当Claude.app添加Cowork支持（从桌面应用进行浏览器自动化）后，引入了一个竞争性的原生消息主机，与Claude Code CLI产生冲突。

Two Native Hosts, Two Socket Formats

两个原生主机，两种套接字格式

Component Native Host Binary Socket Location

Component	Native Host Binary	Socket Location
Claude.app (Cowork)	`/Applications/Claude.app/Contents/Helpers/chrome-native-host`	`/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock`
Claude Code CLI	`~/.local/share/claude/versions/<version> --chrome-native-host`	`$TMPDIR/claude-mcp-browser-bridge-$USER` (single file)

Claude.app (Cowork)

/Applications/Claude.app/Contents/Helpers/chrome-native-host

/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock

Claude Code CLI

~/.local/share/claude/versions/<version> --chrome-native-host

$TMPDIR/claude-mcp-browser-bridge-$USER

(single file)

组件原生主机二进制文件套接字位置

组件	原生主机二进制文件	套接字位置
Claude.app（Cowork）	`/Applications/Claude.app/Contents/Helpers/chrome-native-host`	`/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock`
Claude Code CLI	`~/.local/share/claude/versions/<version> --chrome-native-host`	`$TMPDIR/claude-mcp-browser-bridge-$USER` （单个文件）

Claude.app（Cowork）

/Applications/Claude.app/Contents/Helpers/chrome-native-host

/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock

Claude Code CLI

~/.local/share/claude/versions/<version> --chrome-native-host

$TMPDIR/claude-mcp-browser-bridge-$USER

（单个文件）

Why They Conflict

冲突原因

Both register native messaging configs in Chrome:
- ```
com.anthropic.claude_browser_extension.json
```
  → Claude.app helper
- ```
com.anthropic.claude_code_browser_extension.json
```
  → Claude Code wrapper
Chrome extension requests a native host by name
If the wrong config is active, the wrong binary runs
The wrong binary creates sockets in a format/location the MCP client doesn't expect
Result: "Browser extension is not connected" even though everything appears to be running

两者都会在Chrome中注册原生消息配置：
- ```
com.anthropic.claude_browser_extension.json
```
  → Claude.app助手
- ```
com.anthropic.claude_code_browser_extension.json
```
  → Claude Code包装器
Chrome扩展通过名称请求原生主机
如果错误的配置处于激活状态，就会运行错误的二进制文件
错误的二进制文件会在MCP客户端无法识别的格式/位置创建套接字
结果：即使所有进程看似在运行，仍会提示"Browser extension is not connected"

The Fix: Disable Claude.app's Native Host

修复方案：禁用Claude.app的原生主机

If you use Claude Code CLI for browser automation (not Cowork):

bash

undefined

如果您使用Claude Code CLI进行浏览器自动化（而非Cowork）：

bash

undefined

Disable the Claude.app native messaging config

mv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json
~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json.disabled

Ensure the Claude Code config exists and points to the wrapper

cat ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json


**If you use Cowork (Claude.app) for browser automation:**

```bash

cat ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json


**如果您使用Cowork（Claude.app）进行浏览器自动化：**

```bash

Disable the Claude Code native messaging config

mv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json
~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json.disabled


**You cannot use both simultaneously.** Pick one and disable the other.

mv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json
~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json.disabled


**您无法同时使用两者。** 选择其一并禁用另一个。

Toggle Script

切换脚本

Add this to

~/.zshrc

or run directly:

bash

chrome-mcp-toggle() {
    local CONFIG_DIR=~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts
    local CLAUDE_APP="$CONFIG_DIR/com.anthropic.claude_browser_extension.json"
    local CLAUDE_CODE="$CONFIG_DIR/com.anthropic.claude_code_browser_extension.json"

    if [[ -f "$CLAUDE_APP" && ! -f "$CLAUDE_APP.disabled" ]]; then
        # Currently using Claude.app, switch to Claude Code
        mv "$CLAUDE_APP" "$CLAUDE_APP.disabled"
        [[ -f "$CLAUDE_CODE.disabled" ]] && mv "$CLAUDE_CODE.disabled" "$CLAUDE_CODE"
        echo "Switched to Claude Code CLI"
        echo "Restart Chrome and Claude Code to apply"
    elif [[ -f "$CLAUDE_CODE" && ! -f "$CLAUDE_CODE.disabled" ]]; then
        # Currently using Claude Code, switch to Claude.app
        mv "$CLAUDE_CODE" "$CLAUDE_CODE.disabled"
        [[ -f "$CLAUDE_APP.disabled" ]] && mv "$CLAUDE_APP.disabled" "$CLAUDE_APP"
        echo "Switched to Claude.app (Cowork)"
        echo "Restart Chrome to apply"
    else
        echo "Current state unclear. Check configs:"
        ls -la "$CONFIG_DIR"/com.anthropic*.json* 2>/dev/null
    fi
}

Usage:

chrome-mcp-toggle

then restart Chrome (and Claude Code if switching to CLI).

将以下内容添加到

~/.zshrc

或直接运行：

bash

chrome-mcp-toggle() {
    local CONFIG_DIR=~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts
    local CLAUDE_APP="$CONFIG_DIR/com.anthropic.claude_browser_extension.json"
    local CLAUDE_CODE="$CONFIG_DIR/com.anthropic.claude_code_browser_extension.json"

    if [[ -f "$CLAUDE_APP" && ! -f "$CLAUDE_APP.disabled" ]]; then
        # Currently using Claude.app, switch to Claude Code
        mv "$CLAUDE_APP" "$CLAUDE_APP.disabled"
        [[ -f "$CLAUDE_CODE.disabled" ]] && mv "$CLAUDE_CODE.disabled" "$CLAUDE_CODE"
        echo "Switched to Claude Code CLI"
        echo "Restart Chrome and Claude Code to apply"
    elif [[ -f "$CLAUDE_CODE" && ! -f "$CLAUDE_CODE.disabled" ]]; then
        # Currently using Claude Code, switch to Claude.app
        mv "$CLAUDE_CODE" "$CLAUDE_CODE.disabled"
        [[ -f "$CLAUDE_APP.disabled" ]] && mv "$CLAUDE_APP.disabled" "$CLAUDE_APP"
        echo "Switched to Claude.app (Cowork)"
        echo "Restart Chrome to apply"
    else
        echo "Current state unclear. Check configs:"
        ls -la "$CONFIG_DIR"/com.anthropic*.json* 2>/dev/null
    fi
}

使用方法：运行

chrome-mcp-toggle

，然后重启Chrome（如果切换到CLI，还需重启Claude Code）。

Quick Diagnosis

快速诊断

bash

undefined

bash

undefined

1. Which native host binary is running?

ps aux | grep chrome-native-host | grep -v grep

Claude.app: /Applications/Claude.app/Contents/Helpers/chrome-native-host

Claude Code: ~/.local/share/claude/versions/X.X.X --chrome-native-host

2. Where is the socket?

For Claude Code (single file in TMPDIR):

ls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER" 2>&1

For Claude.app (directory with PID files):

ls -la /tmp/claude-mcp-browser-bridge-$USER/ 2>&1

3. What's the native host connected to?

lsof -U 2>&1 | grep claude-mcp-browser-bridge

4. Which configs are active?

ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic*.json

undefined

ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic*.json

undefined

Critical Insight

关键提示

MCP connects at startup. If the browser bridge wasn't ready when Claude Code started, the connection will fail for the entire session. The fix is usually: ensure Chrome + extension are running with correct config, THEN restart Claude Code.

MCP在启动时建立连接。 如果Claude Code启动时浏览器桥未就绪，整个会话的连接都会失败。通常的修复方法是：确保Chrome和扩展使用正确配置运行，然后重启Claude Code。

Full Reset Procedure (Claude Code CLI)

完整重置流程（Claude Code CLI）

bash

undefined

bash

undefined

1. Ensure correct config is active

mv ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json
~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json.disabled 2>/dev/null

2. Update the wrapper to use latest Claude Code version

cat > ~/.claude/chrome/chrome-native-host << 'EOF' #!/bin/bash LATEST=$(ls -t ~/.local/share/claude/versions/ 2>/dev/null | head -1) exec "$HOME/.local/share/claude/versions/$LATEST" --chrome-native-host EOF chmod +x ~/.claude/chrome/chrome-native-host

3. Kill existing native host and clean sockets

pkill -f chrome-native-host rm -rf /tmp/claude-mcp-browser-bridge-$USER/ rm -f "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER"

4. Restart Chrome

osascript -e 'quit app "Google Chrome"' && sleep 2 && open -a "Google Chrome"

5. Wait for Chrome, click Claude extension icon

6. Verify correct native host is running

ps aux | grep chrome-native-host | grep -v grep

Should show: ~/.local/share/claude/versions/X.X.X --chrome-native-host

7. Verify socket exists

ls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER"

8. Restart Claude Code

undefined

undefined

Other Common Causes

其他常见原因

Multiple Chrome Profiles

多个Chrome配置文件

If you have the Claude extension installed in multiple Chrome profiles, each spawns its own native host and socket. This can cause confusion.

Fix: Only enable the Claude extension in ONE Chrome profile.

如果您在多个Chrome配置文件中安装了Claude扩展，每个配置文件都会生成自己的原生主机和套接字，这可能导致混淆。

修复方案： 仅在一个Chrome配置文件中启用Claude扩展。

Multiple Claude Code Sessions

多个Claude Code会话

Running multiple Claude Code instances can cause socket conflicts.

Fix: Only run one Claude Code session at a time, or use

/mcp

to reconnect after closing other sessions.

运行多个Claude Code实例可能导致套接字冲突。

修复方案： 一次仅运行一个Claude Code会话，或在关闭其他会话后使用

/mcp

重新连接。

Hardcoded Version in Wrapper

包装器中的硬编码版本

The wrapper at

~/.claude/chrome/chrome-native-host

may have a hardcoded version that becomes stale after updates.

Diagnosis:

bash

cat ~/.claude/chrome/chrome-native-host

~/.claude/chrome/chrome-native-host

路径下的包装器可能包含硬编码版本，在更新后会失效。

诊断方法：

bash

cat ~/.claude/chrome/chrome-native-host

Bad: exec "/Users/.../.local/share/claude/versions/2.0.76" --chrome-native-host

Good: Uses $(ls -t ...) to find latest


**Fix:** Use the dynamic version wrapper shown in the Full Reset Procedure above.


**修复方案：** 使用上述完整重置流程中的动态版本包装器。

TMPDIR Not Set

TMPDIR未设置

Claude Code expects

TMPDIR

to be set to find the socket.

bash

undefined

Claude Code需要设置

TMPDIR

才能找到套接字。

bash

undefined

Check

echo $TMPDIR

Should show: /var/folders/XX/.../T/

Fix: Add to ~/.zshrc

export TMPDIR="${TMPDIR:-$(getconf DARWIN_USER_TEMP_DIR)}"

undefined

export TMPDIR="${TMPDIR:-$(getconf DARWIN_USER_TEMP_DIR)}"

undefined

Diagnostic Deep Dive

深度诊断

bash

echo "=== Native Host Binary ==="
ps aux | grep chrome-native-host | grep -v grep

echo -e "\n=== Socket (Claude Code location) ==="
ls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER" 2>&1

echo -e "\n=== Socket (Claude.app location) ==="
ls -la /tmp/claude-mcp-browser-bridge-$USER/ 2>&1

echo -e "\n=== Native Host Open Files ==="
pgrep -f chrome-native-host | xargs -I {} lsof -p {} 2>/dev/null | grep -E "(sock|claude-mcp)"

echo -e "\n=== Active Native Messaging Configs ==="
ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic*.json 2>/dev/null

echo -e "\n=== Custom Wrapper Contents ==="
cat ~/.claude/chrome/chrome-native-host 2>/dev/null || echo "No custom wrapper"

echo -e "\n=== TMPDIR ==="
echo "TMPDIR=$TMPDIR"
echo "Expected: $(getconf DARWIN_USER_TEMP_DIR)"

bash

echo "=== Native Host Binary ==="
ps aux | grep chrome-native | grep -v grep

echo -e "\n=== Socket (Claude Code location) ==="
ls -la "$(getconf DARWIN_USER_TEMP_DIR)/claude-mcp-browser-bridge-$USER" 2>&1

echo -e "\n=== Socket (Claude.app location) ==="
ls -la /tmp/claude-mcp-browser-bridge-$USER/ 2>&1

echo -e "\n=== Native Host Open Files ==="
pgrep -f chrome-native-host | xargs -I {} lsof -p {} 2>/dev/null | grep -E "(sock|claude-mcp)"

echo -e "\n=== Active Native Messaging Configs ==="
ls ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.anthropic*.json 2>/dev/null

echo -e "\n=== Custom Wrapper Contents ==="
cat ~/.claude/chrome/chrome-native-host 2>/dev/null || echo "No custom wrapper"

echo -e "\n=== TMPDIR ==="
echo "TMPDIR=$TMPDIR"
echo "Expected: $(getconf DARWIN_USER_TEMP_DIR)"

File Reference

文件参考

File	Purpose
`~/.claude/chrome/chrome-native-host`	Custom wrapper script for Claude Code
`/Applications/Claude.app/Contents/Helpers/chrome-native-host`	Claude.app (Cowork) native host
`~/.local/share/claude/versions/<version>`	Claude Code binary (run with `--chrome-native-host` )
`~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json`	Config for Claude.app native host
`~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json`	Config for Claude Code native host
`$TMPDIR/claude-mcp-browser-bridge-$USER`	Socket file (Claude Code)
`/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock`	Socket files (Claude.app)

文件	用途
`~/.claude/chrome/chrome-native-host`	Claude Code的自定义包装器脚本
`/Applications/Claude.app/Contents/Helpers/chrome-native-host`	Claude.app（Cowork）的原生主机
`~/.local/share/claude/versions/<version>`	Claude Code二进制文件（需配合 `--chrome-native-host` 运行）
`~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_browser_extension.json`	Claude.app原生主机的配置文件
`~/Library/Application Support/Google/Chrome/NativeMessagingHosts/com.anthropic.claude_code_browser_extension.json`	Claude Code原生主机的配置文件
`$TMPDIR/claude-mcp-browser-bridge-$USER`	套接字文件（Claude Code）
`/tmp/claude-mcp-browser-bridge-$USER/<PID>.sock`	套接字文件（Claude.app）

Summary

总结

Primary issue: Claude.app (Cowork) and Claude Code use different native hosts with incompatible socket formats
Fix: Disable the native messaging config for whichever one you're NOT using
After any fix: Must restart Chrome AND Claude Code (MCP connects at startup)
One profile: Only have Claude extension in one Chrome profile
One session: Only run one Claude Code instance

Original skill by @jeffzwang from @ExaAILabs. Enhanced and updated for current versions of Claude Desktop and Claude Code.

核心问题： Claude.app（Cowork）与Claude Code使用不同的原生主机，且套接字格式不兼容
修复方案： 禁用您不使用的那一方的原生消息配置
修复后操作： 必须重启Chrome和Claude Code（MCP在启动时建立连接）
单配置文件： 仅在一个Chrome配置文件中安装Claude扩展
单会话： 一次仅运行一个Claude Code实例

本技能由@jeffzwang（来自@ExaAILabs）原创，已针对当前版本的Claude桌面端与Claude Code进行增强和更新。

chrome-mcp-troubleshooting

Original

Translation

Claude in Chrome MCP Troubleshooting

Chrome中Claude MCP故障排查

When to Use

适用场景

When NOT to Use

不适用场景

The Claude.app vs Claude Code Conflict (Primary Issue)

Claude.app与Claude Code的冲突（核心问题）

Two Native Hosts, Two Socket Formats

两个原生主机，两种套接字格式

Why They Conflict

冲突原因

The Fix: Disable Claude.app's Native Host

修复方案：禁用Claude.app的原生主机

Disable the Claude.app native messaging config

Disable the Claude.app native messaging config

Ensure the Claude Code config exists and points to the wrapper

Ensure the Claude Code config exists and points to the wrapper

Disable the Claude Code native messaging config

Disable the Claude Code native messaging config

Toggle Script

切换脚本

Quick Diagnosis

快速诊断

1. Which native host binary is running?

1. Which native host binary is running?

Claude.app: /Applications/Claude.app/Contents/Helpers/chrome-native-host

Claude.app: /Applications/Claude.app/Contents/Helpers/chrome-native-host

Claude Code: ~/.local/share/claude/versions/X.X.X --chrome-native-host

Claude Code: ~/.local/share/claude/versions/X.X.X --chrome-native-host

2. Where is the socket?

2. Where is the socket?

For Claude Code (single file in TMPDIR):

For Claude Code (single file in TMPDIR):

For Claude.app (directory with PID files):

For Claude.app (directory with PID files):

3. What's the native host connected to?

3. What's the native host connected to?

4. Which configs are active?

4. Which configs are active?

Critical Insight

关键提示

Full Reset Procedure (Claude Code CLI)

完整重置流程（Claude Code CLI）

1. Ensure correct config is active

1. Ensure correct config is active

2. Update the wrapper to use latest Claude Code version

2. Update the wrapper to use latest Claude Code version

3. Kill existing native host and clean sockets

3. Kill existing native host and clean sockets

4. Restart Chrome

4. Restart Chrome

5. Wait for Chrome, click Claude extension icon

5. Wait for Chrome, click Claude extension icon

6. Verify correct native host is running

6. Verify correct native host is running

Should show: ~/.local/share/claude/versions/X.X.X --chrome-native-host

Should show: ~/.local/share/claude/versions/X.X.X --chrome-native-host

7. Verify socket exists

7. Verify socket exists

8. Restart Claude Code

8. Restart Claude Code

Other Common Causes

其他常见原因

Multiple Chrome Profiles

多个Chrome配置文件

Multiple Claude Code Sessions

多个Claude Code会话

Hardcoded Version in Wrapper

包装器中的硬编码版本

Bad: exec "/Users/.../.local/share/claude/versions/2.0.76" --chrome-native-host

Bad: exec "/Users/.../.local/share/claude/versions/2.0.76" --chrome-native-host

Good: Uses $(ls -t ...) to find latest

Good: Uses $(ls -t ...) to find latest

TMPDIR Not Set

TMPDIR未设置

Check