[BUG] Remote Control bridge fails silently on Desktop app

Open 💬 1 comment Opened Jun 13, 2026 by matt-cudmore

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?

[BUG] Remote Control bridge fails silently on Desktop app — bridge_state: failed — /login Toggle "Enable Remote Control by default" is ON. Every new Desktop session immediately fails with [remote-control] bridge_state: failed — /login. Re-login does not fix it. /login is not available in the Desktop app's Code prompt. Cloud sessions (cse_*) work fine on the same account. OAuth scope in use: user:inference user:file_upload user:profile user:sessions:claude_code. Claude Code 2.1.170, Desktop 1.11187.4, Max plan, Windows 11.

What Should Happen?

Claude on my windows desktop should sync with the cloud and in turn my mac and iphone automatically.

Error Messages/Logs

It just fails to sync

Steps to Reproduce

See above

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Completely fair question, and the honest answer is: you shouldn't need it. The script exists because of a bug. The Desktop app already has a toggle — "Enable Remote Control by default" — which is supposed to do exactly what you want: automatically register every session so your phone and browser can see it, no script required. You turned it on. It silently fails every single time with bridge_state: failed — /login. That's an Anthropic bug specific to your account, not something you did wrong. In a working state, your experience should be: 1. Open a session in the Desktop app on WorkHorse 2. It auto-appears on your iPhone's Code tab and at claude.ai/code on your Mac 3. No script, no terminal, no manual step The script is purely a workaround for that broken toggle. --- There's also a second, deeper limitation worth being honest about: even if the toggle worked perfectly, Remote Control is not true cloud sync. It's a live window into a running process on WorkHorse. The moment WorkHorse sleeps, the sessions disappear from your phone. Your project files never leave your Windows machine. True "always-on, machine-independent" access — where you can open a session on your Mac even with WorkHorse powered off — is a different feature called Claude Code on the web. It runs on Anthropic's cloud infrastructure and connects to a GitHub repo instead of your local files. It's not a replacement for what you've built locally, but it's genuinely cloud-native. --- What you should do right now: File a bug report at github.com/anthropics/claude-code/issues with this exact description: > Remote Control bridge fails silently on Desktop app — bridge_state: failed — /login > Toggle "Enable Remote Control by default" is ON. Every new Desktop session immediately fails with [remote-control] bridge_state: failed — /login. Re-login does not fix it. /login is not available in the Desktop app's Code prompt. Cloud sessions (cse_*) work fine on the same account. OAuth scope in use: user:inference user:file_upload user:profile user:sessions:claude_code. Claude Code 2.1.170, Desktop 1.11187.4, Max plan, Windows 11. That's a precise, reproducible report. Until they fix it, the script is your workaround. Once they fix it, you throw the script away and the toggle does everything automatically.

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗