Claude in Chrome extension fails to connect from Cowork cloud session (desktop app)

Status Closed — duplicate
Maintainer reply None cached
Activity 1 comment · opened Aug 6, 2026 · closed Aug 25, 2026

The claude-in-chrome browser automation tools fail to connect with a persistent "Browser extension is not connected" error, despite completing all documented setup and troubleshooting steps.

Environment:

Claude desktop app (Cowork), session running in the cloud sandbox
Chrome extension "Claude" (Claude in Chrome) — confirmed installed and enabled at chrome://extensions
Account: [monicaretzke@formalabstech.com](mailto:monicaretzke@formalabstech.com), same account used for the Cowork session

Steps taken (in order), with no change in outcome:

Confirmed extension installed and toggle enabled in chrome://extensions
Signed into claude.ai in the same Chrome browser/profile as the extension
Cleared cookies/site data for claude.ai and re-authenticated
Restarted Chrome fully (all windows)
Confirmed "Claude in Chrome" toggle is enabled in desktop app Settings → Connectors, toggled off/on
Retried the connection from the Cowork session multiple times over ~10 minutes

Expected: the Cowork session should be able to reach the browser extension (e.g., via tabs_context_mcp) once the extension is installed, enabled, and the account is signed in on both ends.

Actual: every attempt returns the same error: "Browser extension is not connected. Please ensure the Claude browser extension is installed and running..."

Note: this may be related to open issues #48806 ("Claude in Chrome + Control Chrome Failures in Cowork Mode") and #44541 ("Chrome Connection not possible with Cowork!") — the symptom matches those reports of Cowork-specific connection failures.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗