Claude in Chrome Says Browser Extension Is Not Connected? Fix It

If the Claude in Chrome side panel says it is connected but Claude Code reports Browser extension is not connected, do not start by reinstalling everything or editing Claude's local files. Preserve your active work, update and restart the supported components once, then test a brand-new Claude Code session. If the new session sees the browser, reconnect the Chrome server in the original long-running session with /mcp.

Use this order:

1. Confirm the exact split: the extension looks connected, but Claude Code cannot see a browser.

2. Record non-secret versions and close extra Claude Code sessions.

3. Update and fully restart Chrome, the extension, and Claude Code once.

4. Test a brand-new Claude Code session instead of resuming the failing one.

5. If the new session works, reconnect Claude in Chrome from /mcp in the original session.

6. If both sessions fail, verify the account, Chrome profile, plan, organization policy, and session pairing before escalating.

This sequence follows Anthropic's official restart and update guidance, then adds the stale-session test documented in a resolved August 2026 report. It does not assume that every connection failure has the same cause.

Match the Exact Failure

This guide applies when these signals appear together:

Claude in Chrome side panel: signed in or connected
Claude Code browser check: Browser extension is not connected
list_connected_browsers: [] or no browser
tabs_context_mcp: not connected

The exact tool names may be visible only in diagnostics or Claude's response. The key distinction is simpler: Chrome can run the extension's own side panel, but the active Claude Code process cannot reach the paired browser.

Use a different diagnosis when:

• the extension will not install or sign in;

• Claude can see the browser but cannot access one site;

• a Team or Enterprise administrator disabled Claude in Chrome;

• Chrome shows the extension as disabled;

• Claude Code itself is stuck in an account login loop; or

• you are using Edge, Arc, Brave, or another Chromium browser.

Anthropic currently documents Claude in Chrome for Google Chrome, not other Chromium-based browsers or mobile devices. It also requires a paid Claude plan. If your problem is Claude Code's own browser authorization cycle, diagnose that account login separately.

Prerequisites

Save or finish any command that cannot be interrupted. Do not delete a session or clear the Chrome profile.

Record only non-secret state:

claude --version

In Chrome, open:

chrome://extensions

Turn on Developer mode only if you need to see the installed extension version. Record:

• operating system;

• Chrome version;

• Claude Code version;

• Claude in Chrome extension version;

• whether Claude Code and the extension show the same Claude account;

• the number of open Claude Code sessions; and

• the approximate UTC time of the failed check.

Expected result: you can reproduce the failure without exposing a token, cookie, authorization URL, or browser profile file.

Step 1: Apply the Documented Restart and Update Boundary

Anthropic's current troubleshooting page says to restart or update the Chrome extension when it will not connect to Claude Code, and to restart or update Claude Code as well.

Use one controlled restart:

1. At chrome://extensions, confirm Claude in Chrome is enabled.

2. Update Chrome through Chrome > About Google Chrome if an update is pending.

3. Fully quit Chrome, including all Chrome windows, then relaunch it.

4. Quit the affected Claude Code process and start Claude Code again.

If Chrome manages the extension update automatically, let Chrome apply it. Do not edit Chrome's Secure Preferences file or copy an extension directory by hand.

Expected result: Chrome runs the current installed extension, and Claude Code starts a new process. If the browser becomes visible, stop here.

Step 2: Test a Brand-New Claude Code Session

A resumed conversation can preserve the process or connection context that failed. Open a new terminal and start a brand-new Claude Code session in a safe project directory:

claude

Do not use --resume for this test. Ask the new session to list the connected browser or inspect the current tab without changing the page.

Expected result: either the new session sees the browser, or it fails with the same not-connected state.

If the new session works immediately, the extension, account, and browser are capable of pairing. The failure is isolated to the original long-running Claude Code session. In issue 83320, a fresh session authenticated and saw the paired browser while the older session remained stale.

Step 3: Reconnect the Original Session With /mcp

Return to the original Claude Code session only after the new-session control works. Enter:

/mcp

Open the Claude in Chrome server entry and use the reconnect control shown by your Claude Code version. Then retry one read-only browser check.

Expected result: the original session refreshes its bridge authentication and sees the same paired browser as the fresh session. The August report recovered only after the user authenticated in a fresh session and explicitly reconnected the older session through /mcp.

This is a targeted reconnect, not a general instruction to remove and re-add every MCP server. If /mcp does not show Claude in Chrome, update Claude Code, restart it, and continue with the account and policy checks below.

Step 4: Verify Account, Profile, and Pairing

If a brand-new session also fails, compare the boundaries that can look connected independently.

Same Claude account

Open the extension side panel and Claude Code account status. Confirm both belong to the intended Claude account and organization. Do not paste account identifiers into a public issue.

Supported Chrome profile

Chrome extensions are installed per profile. Open chrome://extensions in the same profile whose tabs you expect Claude Code to control. A healthy extension in a different personal or work profile does not prove that the active profile is paired.

Correct Claude Code session

When several Claude Code sessions are open, the extension can pair to a different terminal. Close sessions you no longer need. If the extension exposes a session selector, choose the session making the browser request.

Plan and organization policy

Anthropic says Claude in Chrome is available on paid plans. Team and Enterprise administrators can disable it or restrict sites. Confirm the connector is allowed before changing local state.

Expected result: one supported Chrome profile, one intended Claude account, and one active Claude Code session agree on the pairing target.

Step 5: Separate Pairing From Site Permissions

Run the smallest read-only test first: list the connected browser or current tab. Do not begin with a login, purchase, form submission, or destructive page action.

If Claude sees the browser but cannot read one page, pairing is working. Check that page's site permission, your organization's site allowlist, and Anthropic's blocked-site categories. The not-connected fix no longer applies.

If Claude cannot see any browser, continue treating this as installation, identity, profile, session, or bridge state. Disabling site protections will not repair a missing browser registration.

Step 6: Stop Local Churn and Escalate

Stop after one restart boundary, one fresh-session control, one /mcp reconnect, and one account/profile/pairing review. Collect:

• the non-secret versions and operating system;

• whether a brand-new session behaved differently from the original;

• whether /mcp listed and reconnected Claude in Chrome;

• whether multiple Claude Code sessions were open;

• whether the same Claude account and Chrome profile were active;

• the exact error wording and UTC time; and

• redacted extension or Claude Code diagnostics requested by Anthropic Support.

Use Claude Code's feedback path or contact Anthropic Support. Link issue 73762 or issue 83320 only when your sequence matches.

Do not edit ~/.claude.json, Chrome Secure Preferences, native-messaging host files, or security software as a first-line fix. Do not disable antivirus or device-management policy globally. Those changes can destroy evidence, weaken the machine, and still leave a stale session untouched.

Common Failure Modes

Why This Fix Works

Claude in Chrome has several observable boundaries: the extension installation, the Claude account, the Chrome profile, the selected Claude Code session, the bridge connection, and the target site's permissions. A connected side panel proves only that part of the extension can run. It does not prove that one long-running terminal still has current bridge state.

The fresh-session test provides a positive control. When it succeeds, the browser, extension, account, and remote pairing can work, leaving the older process as the useful difference. Reconnecting that process through /mcp refreshes the narrow boundary implicated by the comparison. When both sessions fail, the same method redirects attention to account, profile, plan, policy, or installation instead of encouraging destructive cleanup.

This structure applies the repeatable lesson from Aident's Ollama networking guide: name the exact symptom, give the direct answer early, change one boundary at a time, state the expected result, and explain why the test narrows the cause. If the extension remains authorized after logout rather than failing to connect, treat that as a separate access-revocation problem.

Verify One Read-Only Web Action Without a Browser Session

After the Chrome connection is stable, or while it is unavailable, set up Aident Loadout by pasting:

Follow https://aident.ai/SETUP.md

Then ask:

Check my Aident Loadout account authentication and Vault status.
Search the staging capability catalog for a read-only GitHub issue
or web-search Action. Return one current Action's canonical name,
input schema summary, required connection, operation type, and risk level.
Do not execute the provider Action, change a connection, or reveal a secret

Expected result: one current schema-inspected Action, zero provider executions, zero browser-session dependencies, and no API key copied into the prompt. This does not repair Claude in Chrome. It verifies a measurable alternative integration boundary while keeping browser access separate.

Sources

• Claude in Chrome troubleshooting, Anthropic Help Center, accessed August 2, 2026

• Get started with Claude in Chrome, Anthropic Help Center, accessed August 2, 2026

• Extension connected but browser tools stay empty, issue opened and resolved August 2, 2026

• Browser extension is not connected with the same account, issue opened July 3, 2026

• Claude in Chrome permissions guide, Anthropic Help Center, accessed August 2, 2026

Refresh this guide when Anthropic documents the stale-session reconnect directly, changes the /mcp flow, or closes issue 73762 with a verified fix.