[BUG] Browser extension shows "Enabled/Installed" but tools report "not connected"

Status Closed — not planned
Reported on v2.1.20
Maintainer reply None cached
Activity 14 comments · opened Jan 27, 2026 · closed Mar 11, 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?

The /chrome command shows the extension status as "Enabled" and "Installed", but when attempting to use any browser automation tool (like tabs_context_mcp), it fails with "Browser extension is not connected."

What Should Happen?

When the extension shows as Enabled/Installed, browser automation tools should successfully connect to Chrome.

Error Messages/Logs

Browser extension is not connected. Please ensure the Claude browser extension is installed and running (https://claude.ai/chrome).

Steps to Reproduce

  1. Install Claude browser extension from Chrome Web Store
  2. Run claude and enter /chrome - shows Status: Enabled, Extension: Installed
  3. Ask Claude to perform any browser task (e.g., "take a screenshot")
  4. Claude attempts to call tabs_context_mcp and fails with "not connected" error

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.20 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

Environment:

  • Windows
  • Claude Code version: 2.1.20
  • Chrome extension: Installed from official source
  • Tried: Full PC restart, reinstalled extension, checked firewall, reinstalled Claude Code

View original on GitHub ↗

14 Comments

github-actions[bot] · 7 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/20862
  2. https://github.com/anthropics/claude-code/issues/20811
  3. https://github.com/anthropics/claude-code/issues/20786

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

warriorjamez · 7 months ago

Additional Context:

  • Issue started suddenly around 5:30am EST on 2026-01-27
  • Was working before this time
  • No user-initiated changes - broke spontaneously
  • Suggests possible server-side regression or auto-update issue
rvwcs-jimt · 7 months ago

<img width="577" height="375" alt="Image" src="https://github.com/user-attachments/assets/1d9f5964-fa03-49a4-859b-a7062addfc07" />
<img width="476" height="259" alt="Image" src="https://github.com/user-attachments/assets/f65e7334-95c0-47e7-8045-2d5415e988fd" />

I'm having the same issue. New install.

  • Claude 2.1.20
  • Chrome in beta 1.0.40
  • Chrome Version 143.0.7499.170 (Official Build) (64-bit)
  • Microsoft Windows [Version 10.0.26200.7623]
RiaanDeWinnaar · 7 months ago

Same issue. Since running claude install Claude 2.1.20. Claude in chrome no longer works, extension running chrome running, mcp active in claude code. Claude fails when trying to use the tool. Tells me to ,activate the extension.

rvwcs-jimt · 7 months ago

with claude debugging the issue it finds:

● Interesting! The debug logs show the MCP server IS running and it detects your extension (fcoeoabgfenejglbffodgkkbkcdhcgfn) in Chrome's Default profile. The tool calls are completing, but the extension isn't
responding to the native messaging connection.

Let me try one more time now that Chrome has updated:

● Claude in Chrome[tabs_context]
⎿  Tabs read

● Still no luck. The MCP server sees the extension but can't communicate with it.

● Still failing despite everything being configured correctly. This appears to be a bug in the native messaging communication.

Summary of findings:

  • Native messaging host is registered in registry
  • Manifest file exists and is valid
  • Batch file and claude.exe are present
  • Extension is detected in Chrome Default profile
  • MCP tool calls complete but return "not connected"
CHEERFULFRQG · 7 months ago

The same thing, I didn't change anything, and it stopped working around noon. There was a moment when one terminal was working with mcp chrome, but the second one couldn't connect anymore.

JanikBuecher · 7 months ago

Same issue

rvwcs-jimt · 7 months ago

Can also confirm that Chrome integration works fine on this version of claude code on linux, it's only the windows build that's affected

chaseraph · 7 months ago

I have the same issue, also on Windows.

carpcarp · 6 months ago

I spent an hour on this, eventually reinstalling to upgrade to the 2.1.30 worked.

rvwcs-jimt · 6 months ago
I spent an hour on this, eventually reinstalling to upgrade to the 2.1.30 worked.

Anyone else manage to get unstuck here? I'm on 2.1.31 and it's still broken - I've uninstalled and re-installed both claude-code and the extension

rvwcs-jimt · 6 months ago

I think this is fixed now? i can connect claude to chrome again

github-actions[bot] · 5 months ago

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.