You'll notice
Useful2 Signal1
A failed auth token file read now says whether it was empty, missing or blocked by permissions.
What's wrong with this entry?
Anonymous. No account, no email.
What
When Claude Code reads an authentication token from a file at a known location, a failed read now reports a reason instead of just "no token": the file was empty, missing, unreadable due to permissions, or failed for another cause.
Details
- Callers can distinguish "no token configured" from "token exists but cannot be read", which previously looked identical.
Evidence
Read ${s} from well-known file ${e}
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