Claude for Windows cannot connect to Claude in Chrome
Both accounts use the same UUID (8b9cxxxx-...), confirming it's NOT an account mismatch. The real issue is the bridge
rejecting Claude Desktop's OAuth token — it uses scope user:inference user:office but the Chrome bridge endpoint
appears to need user:sessions:claude_code.
This is a Claude Desktop token scope issue. Let me check the version and try forcing a token refresh:
● Bash(cat "C:/Users/ADMIN/AppData/Local/Packages/Claude_pzs8sxrjxfjjc/LocalCache/Roaming/Claude/claude-code/2.1.78/pack age.json" 2>/dev/null | python3 -c "import json…)
⎿ not found 2.1.78
● The root cause is now clear: Claude Desktop is connecting to the bridge at
wss://bridge.claudeusercontent.com/chrome/8b9c0d42-... using an OAuth token with scope user:inference user:office, and the bridge is rejecting it. The bridge likely needs the user:sessions:claude_code scope (which Claude Code CLI has) but Claude Desktop's login flow only requests user:office.
This is not a user configuration problem — it's a token scope mismatch between Claude Desktop's OAuth flow and what
the Chrome bridge endpoint requires.
What you can try:
- Sign out and back in to Claude Desktop — forces a fresh OAuth token that might request updated scopes:
- In Claude Desktop: Settings → Sign out → Sign back in
- Update Claude Desktop — you're using embedded Claude Code v2.1.78 but Claude Code CLI is at 2.1.81. A newer Claude
Desktop might have fixed the scope issue.
- Check for updates in Claude Desktop's settings/menu
- If neither works — this is a confirmed bug. Report it at:
https://github.com/anthropics/claude-code/issues/new?labels=bug,claude-in-chrome
- Include this info: "Claude Desktop bridge connection to wss://bridge.claudeusercontent.com/chrome/ fails with
'Invalid token or user mismatch'. Desktop OAuth token has scope user:inference user:office but bridge requires
user:sessions:claude_code."
The issue is on Anthropic's side — Claude Desktop's OAuth login needs to request the right scope for the Chrome bridge
to work.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗