Remote Control failures are labelled auth or terminal, and auth ones point you at /login.
What's wrong with this entry?
Bridge failures now record whether they were an auth problem or a terminal one, and auth failures show the /login hint. The token-refresh failure message changed from "re-authenticate, then re-enable Remote Control" to text ending "run /login to re-authenticate".
- App state gains an error-kind field alongside the existing error, set to
"auth"or the default"terminal", and cleared wherever the error is cleared.
run /login to re-authenticate
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