[BUG] Claude Code Desktop App (Conductor) – Chrome Extension Connection Failure
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?
conductor will not connect to chrome extension.
What Should Happen?
the chrome extension should connect to conductor the way it has always done and not waste a full days work (unsuccessfully) trying to troubleshoot it
Error Messages/Logs
Still **not connected**. The Chrome extension isn't responding. A few things to check:
1. **Extension installed?** — Visit [claude.ai/chrome](https://claude.ai/chrome) to install it
2. **Logged in?** — You need to be logged into claude.ai in Chrome with the same account running Claude Code
3. **Restart Chrome** — If you just installed the extension, a full Chrome restart is needed
4. **Extension enabled?** — Check `chrome://extensions` and make sure it's toggled on
Let me know once you've checked these and I'll retry.Steps to Reproduce
Summary
The Claude Code desktop application (v2.1.38) cannot connect to the Claude in Chrome browser extension, despite the extension being installed, enabled, and verified as connected. The Claude Code CLI (v2.1.44) connects to the same Chrome extension on the same machine without issues. Cowork also connects fine.
Environment
OS: macOS (Apple Silicon)
Claude Code Desktop App: v2.1.38
Claude Code CLI (brew): v2.1.44
Chrome Extension: Claude in Chrome (Beta) — single extension installed
Browser: Google Chrome
Account: Max Plan
Steps to Reproduce
Install Claude in Chrome extension from Chrome Web Store
Ensure Chrome is running with extension enabled
Open Claude Code desktop app (v2.1.38)
Start a new conversation
Ask Claude to interact with Chrome (e.g., "take a screenshot of my Chrome tab")
Claude responds: "The Chrome extension is not connected"
Expected Behaviour
The desktop app should detect and connect to the Chrome extension, the same way the CLI does.
Actual Behaviour
The desktop app cannot connect. Every new conversation reports the extension is not connected.
Key Finding
Running claude --chrome from Terminal (CLI v2.1.44) and then /chrome shows:
Status: Enabled
Extension: Installed
/mcp shows: claude-in-chrome · ✓ connected
The desktop app (v2.1.38), on the same machine, same Chrome browser, same extension — cannot connect.
Troubleshooting Already Performed
Confirmed extension installed and enabled in chrome://extensions
Confirmed only one Claude extension installed
Restarted Chrome fully (Cmd+Q) multiple times
Restarted desktop app multiple times
Started multiple new conversations
Ensured Chrome was running before launching desktop app
Ran /mcp in desktop app — initially showed "No MCP servers configured"
Ran /chrome in desktop app — returned "Unknown skill: chrome"
Upgraded CLI via brew upgrade claude-code (2.0.76 → 2.1.44)
Ran claude --chrome and /chrome in CLI — Chrome connected successfully
Set "Enabled by default: Yes" in CLI
Verified native messaging host files exist at ~/Library/Application Support/Google/Chrome/NativeMessagingHosts/:
com.anthropic.claude_browser_extension.json ✓
com.anthropic.claude_code_browser_extension.json ✓
Signed out and back into desktop app
After all of the above, /mcp in desktop app terminal shows claude-in-chrome · ✓ connected but the desktop app GUI still reports "Chrome extension is not connected"
Possible Causes
The desktop app (v2.1.38) may bundle its own Claude Code binary separate from the brew CLI (v2.1.44), and its Chrome/MCP integration may have a bug
The desktop app may not read the global Chrome config set by the CLI's /chrome command
Potential account identity mismatch: desktop app authenticates via GitHub OAuth (the only option available), while Chrome's claude.ai uses email sign-in — these may resolve to different internal identities
Issue began ~13 Feb 2026, possibly after an automatic update
Current Workaround
Using claude --chrome from Terminal instead of the desktop app. This works but lacks the desktop GUI features.
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.38 or earlier
Claude Code Version
2.1.44
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
it's related to #24593 and #24539 but they don't cover my specific circumstances/experiences
I'm experiencing the same issue on Windows. Claude Desktop app (v1.1.3363) cannot connect to the Chrome extension — I get a "sign in" popup even though I'm already logged in on both sides with the same account (same email, same org).
Logs confirm the root cause is server-side token rejection:
[Claude in Chrome] WebSocket connected, sending connect message
[Claude in Chrome] Bridge error: Invalid token or user mismatch
[Claude in Chrome] Bridge connection closed (code: 1008, duration: 0ms)
[Chrome Extension MCP] Opened URL in Chrome: chrome-extension://fcoeoabgfenejglbffodgkkbkcdhcgfn/options.html
This has been looping every ~30 seconds since Feb 16. Tried: signing out/in to Desktop app, signing out/in on claude.ai, clearing oauth:tokenCache in config.json — fresh tokens are still rejected by the bridge server.
Environment:
Windows 10 (10.0.26200)
Claude Desktop v1.1.3363 (MSIX/Windows Store)
Chrome extension v1.0.53
Chrome Profile 2 (not Default)
Both Desktop app and claude.ai logged in as same account on org 0ccbba36
The CLI workaround (claude --chrome from a standalone terminal) works fine — the CLI's native host (com.anthropic.claude_code_browser_extension) connects successfully. The issue is specifically with the Desktop app's native host (com.anthropic.claude_browser_extension) and its bridge authentication.
Confirming this bug — Claude Code CLI 2.1.44, Desktop app 1.1.3770
Same symptoms as described. Claude in Chrome extension fails to connect when initiated from Claude Desktop GUI. Confirmed Claude Code CLI version is 2.1.44 (
claude --version), Desktop app is 1.1.3770 (f7f585).The
claude --chromeworkaround via Terminal connects successfully, confirming this is specifically a Desktop GUI / CLI version mismatch issue, not a network or auth problem.Context: Max plan subscriber, macOS. Extension was working earlier in the same day within a Claude Code session inside Desktop, then stopped connecting on subsequent sessions. Same account across both apps.
Would love a fix or a cleaner workaround that doesn't require keeping a Terminal session open. Happy to provide any additional diagnostic info.
Closing for now — inactive for too long. Please open a new issue if this is still relevant.
why would you close it down when you haven't fixed it? the chrome extension STILL isn't connecting with conductor. its been over a month
Same issue here. macOS Sequoia, Claude Code desktop app, Chrome extension v1.0.63. Worked reliably for weeks, broke around 20 March. Extension shows connected in Chrome but tabs_context_mcp always returns not connected. Tried everything — restart Chrome, reconnect extension, switch orgs, create missing native messaging host file. Nothing works. Filed #38845 with full details.
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.