Login tokens are warmed at startup, and skipped entirely for token-based auth.
What's wrong with this entry?
A new start-up step probes the credential version and warms the OAuth token cache through the credentials store, clearing the cached entry if the read comes back empty. It is skipped for token-based auth, including when CLAUDE_CODE_OAUTH_TOKEN or CLAUDE_CODE_OAUTH_TOKEN_FILE_DESCRIPTOR is set, and failures are logged rather than fatal.
Credentials prime through the store failed
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.229
OAuth token warning no longer tells you to unset the variable
Both mention oauth token auth
-
v2.1.234
The CLAUDE_CODE_OAUTH_TOKEN login warning can arrive as its own message
Both mention oauth token auth
-
v2.1.223
Clearer failures when claude.ai project scopes can't be obtained
Both mention oauth token auth