If Remote Control drops due to auth, the notice now tells you to run /login.
What's wrong with this entry?
A disconnect caused by authentication now tells you to re-login instead of offering the generic reconnect hint.
- The disconnect banner takes a cause argument; when the cause is "auth" it appends "run /login to restore Remote Control", unless the message already mentions /login.
- Other causes keep the existing "run /remote-control to reconnect" hint.
- The surrounding REPL-bridge hook was refactored so all teardown paths go through one reset helper taking
archiveAbandoned, replacing several duplicated ref-clearing blocks.
— run /login to restore 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