{"version":"2.1.248","anchor":"token-file-reads-say-why-they-failed","canonical_anchor":"token-file-reads-say-why-they-failed","heading":"Token file reads say why they failed","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/token-file-reads-say-why-they-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Token file reads say why they failed\n\nA failed auth token file read now says whether it was empty, missing or blocked by permissions.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Callers can distinguish \"no token configured\" from \"token exists but cannot be read\", which previously looked identical.\n\n**Evidence**\n\n`Read ${s} from well-known file ${e}`\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}