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.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Token refresh lock timeouts get their own error label

Under the hood
Useful1 Signal1
Auth

Login token refresh lock timeouts get their own error label in logs.

What

When a login token refresh cannot get its lock in time, the failure is now classified as oauth_refresh_lock_timeout rather than falling into the generic bucket, and it is logged the same way as auth errors and revoked tokens. Unconditional.

Evidence

oauth_refresh_lock_timeout

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.248 →