[BUG] Remote Control bridge fails with "/login" on macOS desktop app despite valid claude.ai auth
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?
Summary
/remote-control in the Claude macOS desktop app returns "Remote Control failed to connect: /login" on a Max plan with no API key override. Local sessions started on desktop never appear in the iOS Claude app's Code tab. Sessions started on iOS do appear on desktop — the failure is one-directional, consistent with the desktop-side bridge never registering with the Remote Control service.
Reproduction
- Sign in to Claude macOS desktop app on a Max plan (latest version).
- Settings → Claude Code → enable "Enable remote control by default".
- Start a new Code session on the desktop.
- Type
/remote-controlin the session. - Observe:
Remote Control failed to connect: /login. - Open the iOS Claude app, pull-to-refresh the Code tab. The desktop session is not listed.
Expected
Desktop-started session appears in the iOS Code tab and can be driven remotely.
Logs
From ~/Library/Logs/Claude/main.log, every enable attempt produces:
\````
[info] Enabling remote control for session local_<uuid>
[info] [remote-control] bridge_state: failed — /login
[error] Failed to toggle remote control for local_<uuid>: /login
\
This reproduces across many sessions over multiple hours.
Notably, the same log shows OAuth itself is healthy in the same time window:
\````
[info] claude.ai account active and logged in
[info] [oauth] using cached token for orgId=<orgId>
\
The cached OAuth token's scopes are user:inference user:file_upload user:profile. My speculation (from outside the system) is that the Remote Control bridge requires a scope not present on the cached token, which would explain why the bridge gets a /login redirect despite the rest of the app being authenticated, and why signing out and back in didn't help — the OAuth flow may not be requesting the needed scope.
Tried
- Signed out of all devices and signed back in.
- Toggled "Enable remote control by default" off, full Cmd-Q quit, relaunched, toggled back on.
- Confirmed
ANTHROPIC_API_KEYis unset (only reference in shell config is a commented-out line). - Confirmed no
CLAUDE_CODE_USE_BEDROCK/VERTEX/FOUNDRYoverrides. - Confirmed running latest desktop app version (in-app update check returned "You are running the latest version").
Environment
- Claude desktop app 1.9255.2 (per Sentry baggage in process env)
- macOS
- Max plan
- No API key configured
What Should Happen?
see above
Error Messages/Logs
Steps to Reproduce
see above
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 1.9255.2 (1dc8f7) 2026-05-27T01:57:20.000Z
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
see above
7 Comments
actually I wasn't using Anthropic API, I was using Claude Max 5x
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I've never installed the Claude Code CLI version, so maybe that's the problem.
In case this helps anyone, I've installed the Claude Code Terminal/CLI version, authenticated it with my Claude Max account, and now I can see macOS desktop Claude-created Claude Code sessions on my iPhone Claude app.
Go team!
Adding two corroborating data points that match this server-side RC-credential /
tengu_ccr_bridgegate (not the empty-IndexedDB #59665 variant):/remote-controlfails with "Remote Control failed to connect: /login". Claude Code 2.1.156 inside Claude desktop app 1.9659.2; claude.ai OAuth, noANTHROPIC_API_KEY, clock correct. Regular Claude Code works fine — only Remote Control fails. Re-auth + full app restart didn't help. Anthropic support confirmed "Remote credentials fetch failed".(Consolidating from #64070, auto-flagged as a duplicate of this issue.)
+1 — could Anthropic confirm whether this is the
tengu_ccr_bridgegate, and enable Remote Control for affected Max accounts regardless of platform / billing channel?+1, repro'd this today on Windows; billing via Google Play Store Subscription, causes remote-control feature to not work in Claude Desktop app (no org UUID resolvable).
Also confirming the workaround of installing claude code CLI via winget and running /login there fixed it; claude desktop app didn't even need a restart.
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.