Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Claude in Chrome extension stops connecting spontaneously — MCP 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#46885•Fetched 2026-04-12 13:30:29
View on GitHub
Comments
2
Participants
2
Timeline
8
Reactions
0
Author
joaodeboni-maxjoaodeboni-max
Participants
github-actions[bot]github-actions[bot]joaodeboni-maxjoaodeboni-max
Timeline (top)
labeled ×4commented ×2closed ×1cross-referenced ×1

The Claude in Chrome extension stops connecting spontaneously with no trigger. Once broken, standard troubleshooting does not recover it.

Error Message

Error Messages/Logs

Root Cause

The Claude in Chrome extension stops connecting spontaneously with no trigger. Once broken, standard troubleshooting does not recover it.

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 spontaneously with no trigger. Once broken, standard troubleshooting does not recover it.

What happened

  • MCP shows √ connected for claude-in-chrome
  • Chrome tools return: "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 in mcpServers
  • Restarted Claude Code multiple times
  • claudeInChromeDefaultEnabled: true was already set
  • Port 30900 is listening (process: core) — MCP server running
  • No firewall or port conflicts

Environment

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

What Should Happen?

Chrome extension should stay connected reliably. If connection drops, there should be a way to recover without reinstalling.

Error Messages/Logs

Steps to Reproduce

  1. Set up Claude Code with claudeInChromeDefaultEnabled: true
  2. Use Chrome integration normally
  3. Extension stops connecting spontaneously (no clear trigger)
  4. Reinstalling extension and restarting Claude Code 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

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Session memory saving also broke at the same time, suggesting possible Claude Code state corruption.

extent analysis

TL;DR

The Chrome extension connection issue may be resolved by investigating and addressing potential state corruption in Claude Code, given the simultaneous failure of session memory saving.

Guidance

  • Investigate the relationship between the Chrome extension connection and session memory saving, as the simultaneous failure of both features suggests a possible common cause.
  • Review the Claude Code state management to identify potential corruption or inconsistencies that could be causing the connection issue.
  • Consider resetting or clearing Claude Code's state to see if it resolves the connection problem, while being cautious of potential data loss.
  • Check for any updates or patches for Claude Code version 2.1.104 that may address the regression, as the issue is reported to have worked in a previous version.

Example

No specific code snippet is provided, as the issue seems to be related to the internal state management of Claude Code rather than a specific code error.

Notes

The lack of information about the last working version and specific error messages/logs limits the ability to provide a more targeted solution. Additionally, the potential for state corruption suggests that caution should be taken when attempting to resolve the issue to avoid further data loss or inconsistencies.

Recommendation

Apply workaround: Given the potential for state corruption and the simultaneous failure of session memory saving, it may be necessary to reset or clear Claude Code's state to resolve the connection issue, while being cautious of potential data loss.

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…
#api#pipeline error#runtime error#dependency conflict#environment setup

Still need to ship something?

×6

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

Back to top recommendations

TRENDING