Claude-in-chrome: extension shows connected/enabled in Chrome but tabs_context_mcp reports "not connected" persistently

Status Open
Reported on v2.1.222
Maintainer reply None cached
Activity 0 comments · opened Aug 5, 2026

The Claude in Chrome extension is installed, enabled, and (per the toolbar UI) signed in, but Claude Code's tabs_context_mcp tool call consistently returns "Browser extension is not connected" and never recovers — even after:

  • Toggling the extension off/on
  • Confirming it's enabled in chrome://extensions (screenshot attached)
  • Signing back into the claude.ai account associated with the session

The connection had been working correctly earlier in the same session (browser automation was used successfully to click through a web app, take screenshots, zoom, and run JS via javascript_tool). It dropped at some point mid-session and has not reconnected since, despite the extension itself appearing healthy.

Environment

  • OS: macOS 26.6 (build 25G72)
  • Chrome: 150.0.7871.187
  • Claude Code: 2.1.222

Steps to reproduce

  1. Start a Claude Code session with browser automation working normally (successful tabs_context_mcp, computer, navigate calls).
  2. At some point mid-session (exact trigger unclear — possibly related to a /login re-authentication or a page navigation that logged out of an app being tested), the connection drops.
  3. Subsequent tabs_context_mcp calls return: "Browser extension is not connected. Please ensure the Claude browser extension is installed and running..."
  4. Confirmed extension is installed and enabled via chrome://extensions (see screenshot).
  5. Retried tabs_context_mcp multiple times over an extended period — no change.

Expected behavior
Either the connection recovers automatically, or the extension/tool surfaces a more
actionable error (e.g., distifrom "installed but handshakefailed") so the user knows whether to restart Chrome, re-auth, or something else.

Actual behavior
Extension appears healthy in connection neverre-establishes without a manual fix that I don't yet know (a Chrome restart was suggested but not yet confirm

Screenshot
<img width="689" height="491" alt="Image" src="https://github.com/user-attachments/assets/e4dd57de-4bb9-40c1-9c1c-c8b2cefe74eb" />

View original on GitHub ↗