Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude in Chrome: bridge pairing state broken server-side for 7+ weeks — account-level reset needed [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56241•Fetched 2026-05-06 06:33:24
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
jaketheeditorjaketheeditor
Participants
jaketheeditorjaketheeditor
Timeline (top)
labeled ×4

Error Message

The Claude in Chrome extension cannot connect to Claude Desktop. Error shown:

Error Messages/Logs

Code Example

mcp__Claude_in_Chrome__list_connected_browsers  → "Claude in Chrome is not connected"
mcp__Claude_in_Chrome__tabs_context_mcp         → "Claude in Chrome is not connected"
mcp__Claude_in_Chrome__switch_browser           → "Claude in Chrome is not connected"
                                                   (no Connect dialog appeared in Chrome)
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

First observed: mid-March 2026 | Duration: 6+ weeks Related issues: #48806, #52367, #24593

The Claude in Chrome extension cannot connect to Claude Desktop. Error shown:

"Check your Claude in Chrome account — The Chrome extension needs to be signed in with the same account as Claude Desktop."

Both apps are signed into the same account. This dialog has never not appeared.

Why this is server-side (not local) The switch_browser MCP tool broadcasts a connection request and waits up to 2 minutes for the user to click Connect. No dialog appears on my machine. The broadcast is not reaching my extension at all.

Separately: the Control Chrome MCP (non-Anthropic infrastructure) successfully lists tabs in the same Chrome session that Claude in Chrome cannot reach. The local Chrome install is fully operational. The failure is isolated to bridge.claudeusercontent.com.

Client-side work completed Full Chrome uninstall/reinstall including all profile data, caches, preferences, and saved state. Single native messaging host present (com.anthropic.claude_browser_extension.json). No conflicting hosts, no enterprise policies, no VPN, no interfering extensions. Issue persists across every rebuild.

Support status Anthropic support has acknowledged in writing that this requires "a human agent with backend access to investigate the bridge pairing state." No engineer has acted on it in 6+ weeks. Latest response sent was a generic remote MCP server / firewall template unrelated to the Chrome extension bridge.

What Should Happen?

Server-side reset of the bridge pairing state for my account. Support ticket has stalled — posting here to reach the team that owns the Chrome extension bridge infrastructure directly.

Error Messages/Logs

mcp__Claude_in_Chrome__list_connected_browsers  → "Claude in Chrome is not connected"
mcp__Claude_in_Chrome__tabs_context_mcp         → "Claude in Chrome is not connected"
mcp__Claude_in_Chrome__switch_browser           → "Claude in Chrome is not connected"
                                                   (no Connect dialog appeared in Chrome)

Steps to Reproduce

try to connect to mcp server.

Claude Model

Not sure / Multiple models

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

Claude 1.5354.0 (9a9e3d) 2026-04-29T01:14:34.000Z

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely due to an incorrect bridge pairing state on the server-side, which can be resolved by resetting the bridge pairing state for the affected account.

Guidance

  • The error message suggests that the Chrome extension and Claude Desktop are not connected, despite being signed in with the same account, indicating a potential issue with the bridge pairing state.
  • The fact that the Control Chrome MCP tool can list tabs in the same Chrome session, but the Claude in Chrome extension cannot, suggests that the issue is isolated to the bridge.claudeusercontent.com infrastructure.
  • To verify the issue, try connecting to the mcp server and check if the "Claude in Chrome is not connected" error message appears.
  • Reach out to the Anthropic support team again, providing the error messages and logs, and request a server-side reset of the bridge pairing state for the affected account.

Example

No code snippet is provided as it is not necessary for this issue.

Notes

The issue has been ongoing for 6+ weeks, and the support team has acknowledged that it requires a human agent with backend access to investigate the bridge pairing state. However, no engineer has acted on it yet.

Recommendation

Apply workaround: Reach out to the Anthropic support team again and request a server-side reset of the bridge pairing state for the affected account, as this is the most likely solution to resolve the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#prompt template#agent execution#callback error#memory management

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING