Desktop: Remote Control is not restored after app update/restart for existing sessions, and sessions silently disappear from mobile while the app still reports "connected"

Status Open
Maintainer reply None cached
Activity 2 comments · opened Oct 8, 2026

Environment: Claude Desktop for Windows 11 (build 2.26454.0.0), Code tab, Remote Control used from the Claude mobile app.

Symptoms

  1. After the app auto-updates and relaunches, all sessions that had Remote Control on are stopped, and Remote Control is NOT re-enabled for existing sessions. They disappear from the mobile app until I manually toggle Remote Control per session.
  2. Even without a restart, existing sessions silently disappear from the mobile app after being idle for hours (overnight). main.log shows no disconnect, and the last bridge_state is still "connected", and the PC did not sleep (no Kernel-Power sleep events, AC sleep timeout is 0). Toggling Remote Control off/on in the app makes them reappear.
  3. Settings > Claude Code > "Connect new sessions to Remote Control" only affects sessions created after the change, so it does not fix 1 or 2 for existing long-lived sessions.
  4. I tried to automate "toggle off/on" with a scheduled task, but set_remote_control requires an in-app approval that an unattended scheduled run cannot get (the run ends in ~20s as "not approved"), and adding an allow rule for the tool in settings.json did not help.

Expected

  • Sessions that had Remote Control on should be reconnected automatically after an app update/restart.
  • The mobile app should keep showing connected sessions, or the desktop app should detect a stale bridge and reconnect (heartbeat/auto re-register).
  • If a setting exists, it should also apply to existing sessions, or there should be a supported way to let scheduled tasks re-register Remote Control.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗