{"version":"2.1.315","anchor":"oauth-token-orgaccount-failure-reasons-recognised","canonical_anchor":"oauth-token-orgaccount-failure-reasons-recognised","heading":"Three new sign-in failure reasons for tokens without an organization or account","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/oauth-token-orgaccount-failure-reasons-recognised","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Three new sign-in failure reasons for tokens without an organization or account\n\nClaude Code now recognises sign-in failures where the token has no organization, has no account, or the account is not a member\n\n**What**\n\nWhen signing in with OAuth (the browser-based login to your Anthropic account) fails, Claude Code sorts the failure into a reason. It now recognises three more reasons:\n\n- the token has no organization\n\n- the token has no account\n\n- the account is not a member\n\nEach has a long form, such as `oauth_account_not_member`, and a matching short form.\n\n**Why**\n\nAccounts that hit one of these cases may now get a specific sign-in error instead of a generic one.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}