Claude in Chrome extension: tabs_context_mcp persistently reports "not connected" despite extension appearing logged in and running

Summary

The Claude in Chrome browser extension tools (via Claude Code) consistently fail with "Browser extension is not connected"
errors, even though the extension appears installed, running, and logged into claude.ai in Chrome.

## Steps to reproduce

1. Have an active Claude Code session using Claude in Chrome browser automation tools (was mid-session, had successfully

used the extension for an extended period before this occurred).

1. At some point during the session, browser tool calls (e.g. tabs_context_mcp) started failing with:

(https://claude.ai/chrome), and that you are logged into claude.ai with the same account as Claude Code..."

1. Retried tabs_context_mcp (with createIfEmpty:true and false) multiple times (5+ attempts across several minutes) — same

error every time.

1. Confirmed on my end that the Chrome extension icon shows as installed/active and I'm logged into claude.ai.

## Expected behavior
Either the extension reconnects automatically, or the tool call succeeds once the extension is confirmed running/logged
in.

## Actual behavior
Every retry returns the identical "not connected" error, with no visible change in behavior regardless of extension state
on the Chrome side.

## Environment

• Platform: macOS (Darwin)
• Claude Code (CLI)
• Claude in Chrome extension

## Additional context
This occurred mid-session after extensive prior successful use of the browser automation tools (many tabs_create_mcp,
navigate, javascript_exec, computer calls had worked fine before this). The disconnect appears to have happened
spontaneously, not tied to a specific action.