[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
- Install Claude browser extension from Chrome Web Store
- Run claude and enter /chrome - shows Status: Enabled, Extension: Installed
- Ask Claude to perform any browser task (e.g., "take a screenshot")
- 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
14 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Additional Context:
<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.
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.
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:
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.
Same issue
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
I have the same issue, also on Windows.
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
I think this is fixed now? i can connect claude to chrome again
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
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.