Remote Control now retries reconnecting with backoff and tells you to run /login when auth fails.
What's wrong with this entry?
Credential re-mint after a transport close now retries with exponential backoff instead of giving up, and authentication failures get their own terminal messages telling you exactly which command to run.
- Backoff uses a 30s base with a 300s cap, showing "Remote Control server unreachable — retrying (attempt N)".
- A rejected credential forces one OAuth refresh before the next attempt.
- Terminal failures direct the user to run /login and then /remote-control.
Claude.ai login expired — run /login, then /remote-control
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.222
MCP server panel explains a rejected claude.ai session token
Both mention login
-
v2.1.222
MCP: rejected claude.ai session token is now visible
Both mention login
-
v2.1.222
Dedicated error when claude.ai rejects a session bearer token
Both mention login