Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Remote Control not auto-restored after mid-session re-login (even with 'enable for all sessions' on) [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#47000•Fetched 2026-04-13 05:44:09
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Author
rany-antrany-ant
Participants
rany-antrany-ant
Timeline (top)
labeled ×4closed ×1commented ×1
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

Re-enable Remote Control after mid-session re-authentication by running the /remote-control command or by modifying the authentication flow to automatically re-establish the Remote Control bridge.

Guidance

  • Verify that the "Enable Remote Control for all sessions" setting is set to true in /config to ensure it applies at session startup.
  • After re-authenticating mid-session, check the Remote Control status to confirm it has been disabled.
  • Run the /remote-control command to manually re-enable Remote Control after re-authentication.
  • Consider modifying the re-authentication flow to print a notice when Remote Control is disconnected, prompting the user to run /rc to reconnect.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The current implementation only applies the "Enable Remote Control for all sessions" setting at session startup, not after mid-session re-authentication. This limitation may require changes to the authentication flow or the Remote Control configuration.

Recommendation

Apply a workaround by running the /remote-control command after re-authentication, as the current implementation does not automatically re-enable Remote Control mid-session.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

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.

#SSR setup#ISR setup#authentication setup#request error#file not found

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Remote Control not auto-restored after mid-session re-login (even with 'enable for all sessions' on) [1 comments, 1 participants]