{"version":"2.1.314","anchor":"gateway-login-rolls-back-the-stored-credential-if-the-sign-i","canonical_anchor":"gateway-login-rolls-back-the-stored-credential-if-the-sign-i","heading":"Failed or cancelled gateway sign-ins no longer leave the wrong credential saved","tier":"notice","area":"Gateway Proxy","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/gateway-login-rolls-back-the-stored-credential-if-the-sign-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Failed or cancelled gateway sign-ins no longer leave the wrong credential saved\n\nIf a gateway sign-in fails or is replaced by another, Claude Code puts back the previous credential and removes the undone one\n\n**What**\n\nA gateway is a server that Claude Code signs in to and sends its requests through. Saving a gateway sign-in now works as an all-or-nothing step. If the save fails, or another sign-in replaces it, Claude Code:\n\n- restores the credential and allowlist entry that were there before\n\n- removes the undone credential from where credentials are stored, including secure storage\n\n- skips revoking that credential when it belongs to the account still signed in at that gateway\n\nBefore, the save was a single write that stopped with an error on failure and had nothing to put back.\n\n**Why**\n\nCancelling or failing a gateway sign-in now leaves you signed in as you were, rather than with the wrong credential saved.\n\n- Area: Gateway Proxy\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}