{"version":"2.1.309","anchor":"env-credential-read-failure-fallback-now-uses-a-helper-inste","canonical_anchor":"env-credential-read-failure-fallback-now-uses-a-helper-inste","heading":"Fallback after credential read errors now uses a different check","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/env-credential-read-failure-fallback-now-uses-a-helper-inste","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Fallback after credential read errors now uses a different check\n\nWhen Claude Code can't read its credentials because of a permission error, a different check now decides whether to try a fallback\n\n**Unclear.** It is not clear whether the new check gives the same answer as the old one, especially in remote sessions.\n\n**What**\n\nSometimes Claude Code cannot read its stored credentials because the system refuses permission (the errors `EACCES` or `EPERM`). In that case it can try a fallback. Before, it tried the fallback only when `CLAUDE_CODE_REMOTE` was not set and Claude Code had not been started by another program over a direct message channel. That decision is now made by a separate check.\n\n**Why**\n\nThis may simply be a rewrite with no effect. It may also change whether the fallback runs in remote sessions.\n\n- Area: Auth\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}