{"version":"2.1.319","anchor":"auth-failure-cause-reporting-changed-to-gatewayno-creds-str","canonical_anchor":"auth-failure-cause-reporting-changed-to-gatewayno-creds-str","heading":"Missing-credential errors now tell gateway use apart from having no credentials","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/auth-failure-cause-reporting-changed-to-gatewayno-creds-str","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Missing-credential errors now tell gateway use apart from having no credentials\n\nWhen no credentials are found, Claude Code now records the reason as either gateway use or no credentials, and drops one old label\n\n**Unclear.** Where the message text shown to you about missing credentials now comes from, and what it says.\n\n**What**\n\nWhen Claude Code finds no credentials, meaning no login or key it can use, it works out a reason. That reason is now either \"gateway\" or \"no_creds\". A gateway is a server placed between Claude Code and the model provider. The label \"no Anthropic credentials\" is no longer produced at this point.\n\nWhen Claude Code detects that it is running through a gateway, it also ignores API keys that fail a check.\n\n**Why**\n\nThe wording you see about missing credentials, or about using a gateway, may change.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}