Claude Code v2.1.225 ·
Remote Control bridge: token-refresh exhaustion now surfaces a login prompt
When remote control can't refresh your token, it now tells you to run /login instead of stalling.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
New FeaturesKind: in v2.1.225,
New FeaturesSection of the release
What
When the bridge runs out of token-refresh retries, the session is marked failed with an instruction to run /login instead of stalling silently.
Details
- The refresher gained an
onExhausted callback fired after the configured number of consecutive failures, logged at error level - Existing "Refresh chain exhausted for sessionId=" logging and
bridge_token_refresh_exhausted telemetry are unchanged - The bridge supplies the callback and moves the session into a failed/auth state carrying the user-facing reason
- Token-refresh failures inside
getAccessToken are now caught and logged rather than thrown - A new
cred_4094_recovery cause joins the recovery connect-timeout classification
Evidence
OAuth token unavailable \u2014 run /login to restore Remote Control, run /login to restore Remote Control
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.225 →
