Remote Control not auto-restored after mid-session re-login (even with 'enable for all sessions' on)

Resolved 💬 2 comments Opened Apr 12, 2026 by rany-ant Closed Apr 12, 2026

Problem

When the OAuth token expires mid-session and you re-authenticate (via /login or claude auth login), Remote Control is silently disabled in that session. You have to notice and manually run /remote-control to re-enable it.

This happens even when "Enable Remote Control for all sessions" is set to true in /config — that setting only applies at session startup, not after a mid-session re-auth.

Expected behavior

If the persistent "Enable Remote Control for all sessions" setting is on, re-authenticating mid-session should automatically re-establish the Remote Control bridge, the same way a fresh session would.

At minimum, print a notice after re-login that Remote Control was disconnected and needs /rc to reconnect — currently it fails silently.

Repro

  1. /config → set "Enable Remote Control for all sessions" = true
  2. Start a session; confirm Remote Control is connected
  3. Let the token expire (or force it: claude auth logout in another terminal)
  4. Re-auth in the running session via /login
  5. Remote Control is now disconnected; /rc is required to restore it

Related

  • #36807 covers the upstream problem (token expiry forces interactive re-login on the host). This issue is the downstream gap: even after you do re-login, RC doesn't come back on its own.

Environment

  • homespace (linux), enterprise plan, OAuth auth

View original on GitHub ↗

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