Under the hood
Useful1 Signal2
Figuring out where your auth token came from is now asynchronous and returns both token forms together.
What's wrong with this entry?
Anonymous. No account, no email.
What
The helper that classified a token as coming from the credential store, the environment or a file descriptor no longer reads the store synchronously; callers await it and it returns the bearer token and file-descriptor token together. The organization UUID check and one startup task became asynchronous to match.
Evidence
CLAUDE_CODE_ORGANIZATION_UUID
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.234
Signing back into the same account keeps a pending auto-resume
Both mention auth
-
v2.1.234
Token screen reports actual remaining validity
Both mention auth
-
v2.1.234
Setup-token login result carries the expiry
Both mention auth