Claude in Chrome extension stops connecting spontaneously — MCP connected but extension reports not connected
Resolved 💬 3 comments Opened Apr 12, 2026 by joaodeboni-max Closed Apr 12, 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?
Description
The Claude in Chrome extension stops connecting spontaneously with no trigger. Once broken, standard troubleshooting does not recover it.
What happened
- MCP shows
√ connectedforclaude-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
- Set up Claude Code with claudeInChromeDefaultEnabled: true
- Use Chrome integration normally
- Extension stops connecting spontaneously (no clear trigger)
- 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.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗