{"version":"2.1.304","anchor":"sdk-headless-login-rolls-back-on-refused-orgprovider","canonical_anchor":"sdk-headless-login-rolls-back-on-refused-orgprovider","heading":"A refused login no longer has to log you out","tier":"notice","area":"Auth","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/sdk-headless-login-rolls-back-on-refused-orgprovider","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### A refused login no longer has to log you out\n\nWhen an app's sign-in is refused because of provider or organisation rules, Claude Code now tries to restore the previous login\n\n**What**\n\nWhen a sign-in started through `claude_authenticate` is refused, because the provider is not allowed or the organisation does not match, Claude Code now tries to restore the login that was there before, or to revoke the new one, before reporting the failure. The error it reports depends on which of those worked. Before, it cleared the saved login and reported one error.\n\n**Why**\n\nA refused sign-in no longer necessarily leaves you logged out.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}