claude-code - 💡(How to fix) Fix Claude in Chrome extension stops connecting spontaneously — MCP shows connected but extension reports not connected [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46886Fetched 2026-04-12 13:30:26
View on GitHub
Comments
2
Participants
2
Timeline
9
Reactions
0
Timeline (top)
labeled ×5commented ×2closed ×1cross-referenced ×1

The Claude in Chrome extension stops connecting to Claude Code spontaneously, with no clear trigger. Once broken, it cannot be recovered through standard troubleshooting.

Error Message

Error Messages/Logs

Error when using Chrome: "A extensão ainda não está conectada. Verifique: 1. Extensão instalada? 2. Extensão ativa? 3. Logado no claude.ai? 4. Reiniciou o Chrome?"

Root Cause

Session memory/conversation saving also stopped working at the same time as the Chrome connection issue, suggesting possible Claude Code state corruption or a shared root cause.

Code Example

MCP status: √ connected
Error when using Chrome: "A extensão ainda não está conectada. Verifique: 1. Extensão instalada? 2. Extensão ativa? 3. Logado no claude.ai? 4. Reiniciou o Chrome?"

netstat output: TCP 127.0.0.1:30900 LISTENING (process: core)
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Description

The Claude in Chrome extension stops connecting to Claude Code spontaneously, with no clear trigger. Once broken, it cannot be recovered through standard troubleshooting.

What happened

  • MCP shows √ connected for claude-in-chrome
  • Every Chrome tool call returns: "A extensão ainda não está conectada"
  • Session memory/conversation saving stopped at the same time

What I tried (none worked)

  • Extension installed and enabled in chrome://extensions/
  • Logged into claude.ai in Chrome with correct account
  • Completely uninstalled and reinstalled the Chrome extension
  • Removed and re-added claude-in-chrome entry in mcpServers
  • Restarted Claude Code multiple times
  • claudeInChromeDefaultEnabled: true was already set in settings.json
  • Port 30900 confirmed listening (process: core) — MCP server running
  • No firewall or port conflicts found

Environment

  • OS: Windows 11 / PowerShell
  • MCP server listening on 127.0.0.1:30900

What Should Happen?

Chrome extension should connect and stay connected reliably across sessions. If connection drops, there should be a recoverable path without full reinstall.

Error Messages/Logs

MCP status: √ connected
Error when using Chrome: "A extensão ainda não está conectada. Verifique: 1. Extensão instalada? 2. Extensão ativa? 3. Logado no claude.ai? 4. Reiniciou o Chrome?"

netstat output: TCP 127.0.0.1:30900 LISTENING (process: core)

Steps to Reproduce

  1. Set up Claude Code with claudeInChromeDefaultEnabled: true
  2. Use Chrome integration normally for some time
  3. Extension stops connecting spontaneously with no clear trigger
  4. Restarting Claude Code and reinstalling the extension does not fix it

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.104 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Session memory/conversation saving also stopped working at the same time as the Chrome connection issue, suggesting possible Claude Code state corruption or a shared root cause.

extent analysis

TL;DR

The Chrome extension connection issue with Claude Code may be resolved by investigating and addressing potential state corruption or a shared root cause affecting both the extension connection and session memory/conversation saving.

Guidance

  • Investigate the relationship between the Chrome extension connection and session memory/conversation saving, as they seem to be affected simultaneously, suggesting a shared root cause.
  • Review the Claude Code settings and configuration to ensure that there are no inconsistencies or misconfigurations that could be contributing to the issue.
  • Consider checking the Anthropic API integration and platform settings to ensure they are correctly set up and compatible with the current version of Claude Code.
  • Since this is reported as a regression, comparing the current configuration and settings with those from the last known working version might provide insights into what changed and how to revert or adjust the settings to resolve the issue.

Example

No specific code snippet can be provided without more detailed information about the integration or the exact changes made between versions. However, reviewing the settings.json file for any changes or inconsistencies, especially related to claudeInChromeDefaultEnabled, might be a good starting point.

Notes

The lack of information about the last working version and any specific changes made to the system or Claude Code configuration limits the ability to provide a precise fix. The issue seems complex and might require deeper investigation into the state of Claude Code and its integrations.

Recommendation

Apply workaround: Given the complexity and the potential for state corruption or a shared root cause, applying a workaround such as regularly restarting Claude Code or temporarily disabling and re-enabling the Chrome extension might provide a temporary solution until a more permanent fix can be found. This approach is recommended due to the lack of clear triggers for the issue and the need for further investigation to identify a root cause.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING