Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.225 Home All releases ←olderv2.1.224 v2.1.226newer→
Claude Code v2.1.225

Remote Control bridge: token-refresh exhaustion now surfaces a login prompt

You'll notice
Useful3 Signal0
Remote Control

When remote control can't refresh your token, it now tells you to run /login instead of stalling.

/login
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.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.225 →