Some sign-in errors on side requests no longer trigger a token refresh
Some background requests now skip the login token refresh on certain sign-in errors, and the log message for a failed refresh reports the right details
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.309,
ImprovementsSection of the release
Unclear Which sign-in errors now skip the token refresh is not stated.
What
Besides the main conversation, Claude Code sometimes sends smaller side requests to the model. When one of these fails with a sign-in error, Claude Code normally tries to refresh your login token (the credential that proves you are signed in) and retry. For a particular kind of failure it now skips the refresh and reports the error straight away.
The log message written when a refresh attempt fails now reports the correct status and details. Before, it read from the wrong values.
Why
Some sign-in errors on these side requests no longer cause a pointless refresh attempt. If you read Claude Code's logs while tracking down a sign-in problem, the refresh failure message now describes what actually happened.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich sign-in errors now skip the token refresh is not stated.
