Claude in Chrome: extension shows as connected/ready but Cowork/Dispatch can't use it, and Chrome conversations don't sync to Desktop sidebar

Status Fixed / completed
Reported on v2.1.210
Maintainer reply None cached
Activity 0 comments · opened Jul 19, 2026 · closed Jul 22, 2026

Preflight Checklist

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

What's Wrong?

Two symptoms on the same macOS machine that both point to a broken link between Claude Desktop (Cowork/Dispatch) and the Claude in Chrome extension, even though the extension itself looks healthy:

  1. Claude in Chrome conversations don't appear in Claude Desktop's sidebar.

Conversations held in the Claude in Chrome side panel in the browser never show up in Claude Desktop's left-hand conversation list, despite both being signed into the same Anthropic account.

  1. Dispatch's "ready to use Chrome" check doesn't translate into a working connection.

On the Dispatch onboarding screen ("Get ready to dispatch"), "Claude is ready to use Chrome" is displayed as a checkmark rather than a toggle (unlike "Keep this computer awake" and "Let Claude control your computer," which are interactive toggles). This implies the extension registers as connected to Anthropic's cloud, but it's unclear whether Dispatch/Cowork can actually drive Chrome through that connection.

Verified:

Same Anthropic account is signed into both Claude Desktop and the Claude in Chrome extension.
Claude in Chrome extension is installed and enabled.

Not yet verified / would help narrow this down:

Whether Claude Code CLI is also installed on this machine (a known compounding cause — see related issues below)
Extension service-worker network log (WebSocket status to the Anthropic bridge)
Exact error returned by Dispatch/Cowork's own Chrome tool calls (e.g. list_connected_browsers)

Related issues

This matches the pattern already reported in:

#56241 — bridge pairing state reportedly broken server-side; issue remains open/unassigned, and per the report, Anthropic support acknowledged it needs backend investigation but no fix had landed as of the last update
#36626 — Cowork shows "Check your Claude in Chrome account" despite matching accounts and healthy local native messaging
#48806 — extension pairs fine in-browser, but the Cowork session never receives the handshake
#58968 — side panel works (talks to Anthropic's cloud directly) but list_connected_browsers still reports not connected
#33483, #55209, #54567, #45318, #58201 — native-messaging-host race condition when Claude Code CLI is installed alongside Claude Desktop (Desktop's host wins the connection every time)

What Should Happen?

Claude Desktop's Dispatch/Cowork should reliably detect and use an already-connected Claude in Chrome extension, and Claude in Chrome conversation history should sync into the Claude Desktop sidebar for the same account.

Environment

OS: macOS [version — fill in]
Claude Desktop version: [fill in — Settings → About]
Claude in Chrome extension version: [fill in — chrome://extensions]
Chrome version: [fill in]
Claude Code CLI also installed on this machine?: [Yes/No — fill in]
Account type: [Personal/Pro/Max/Team/Enterprise — fill in]

Error Messages/Logs

Steps to Reproduce

Sign into Claude Desktop and the Claude in Chrome extension with the same account.
Have one or more conversations in the Claude in Chrome side panel in the browser.
Open Claude Desktop and check the left sidebar — the Chrome conversations are missing.
Open Dispatch setup ("Get ready to dispatch") — "Claude is ready to use Chrome" shows as a checkmark, not a toggle.
Try to have Dispatch/Cowork perform a task that requires Chrome

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.210

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗