An expired Remote Control credential now closes with a clear message telling you to run /login.
What's wrong with this entry?
Remote Control now separates auth failures from other disconnects. When the worker token expires or is rejected, the session closes with a dedicated code and the message points you at /login, instead of the previous generic re-authenticate wording.
- New close code
4094, "worker credential expired or rejected (code 4094)", used fortoken_expiredandauth_exhausted. epoch_conflict,epoch_staleandsession_not_foundkeep close code4090and recover through the poll loop.- The cause-based mapping applies only when the transport is built with
causeTypedCloseCodes; both v2 bridge call sites pass it as true, so it is live. - The 404-exhaustion path now names its cause explicitly as
session_not_found.
worker credential expired or rejected (code 4094)
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