Feature request: register Remote Control for all sessions at once - registrations don't survive app restart

Status Open
Maintainer reply None cached
Activity 1 comment · opened Aug 27, 2026

On the Windows desktop app (Microsoft Store install, observed since 1.25927.0.0), Remote Control registration is effectively per-session, per-app-run:

  • The "enable remote control by default" toggle only auto-registers sessions created during the app run in which it was switched on. After any restart, newly created sessions no longer auto-register, even with the toggle still on (verified via main.log: no "Enabling remote control" lines at creation times).
  • Every app restart silently wipes all registrations, manual and automatic alike. Sessions remain visibly healthy but are unreachable from claude.ai/code until /remote-control is re-run in each one.
  • /remote-control is user-only (sessions cannot invoke it for themselves), so for a workspace with ~20 long-running sessions, every restart means manually visiting every chat and retyping the command - and there is no indicator of which sessions are currently registered.

Request: a single "enable Remote Control for all sessions" action (or making the existing default toggle re-register sessions on every app start), plus ideally a visible per-session registered/unregistered state.

Happy to provide main.log extracts. Environment: Windows 11 Pro, Claude Desktop via Microsoft Store; behaviour first established 5 Aug 2026 by systematic elimination and still present on the current build (27 Aug 2026).

View original on GitHub ↗

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