{"version":"2.1.286","anchor":"auth-source-classification-changed-login-managed-key","canonical_anchor":"auth-source-classification-changed-login-managed-key","heading":"Keys managed through \/login are now labelled as API keys, not claude.ai","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/auth-source-classification-changed-login-managed-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Keys managed through \/login are now labelled as API keys, not claude.ai\n\nClaude Code now reports a key managed through `\/login` as an API key rather than a claude.ai login\n\n**Unclear.** It is not certain the other conditions that lead to the API key label are exactly the same as before.\n\n**What**\n\nClaude Code keeps a label for where your sign-in credentials came from. A key managed through `\/login` used to be labelled as a claude.ai login. It is now labelled as an API key (a secret key used to access Anthropic's API directly). Any request that uses `ANTHROPIC_API_KEY` is also labelled as an API key.\n\n**Why**\n\nThe label decides how your sign-in type is shown and recorded, so a `\/login`-managed key now appears as an API key wherever that label is used.\n\n- Area: Auth\n- Names: `\/login`, `ANTHROPIC_API_KEY`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}