{"version":"2.1.319","anchor":"401-handling-distinguishes-stale-responses","canonical_anchor":"401-handling-distinguishes-stale-responses","heading":"Sign-in refusals for an old credential are now ignored","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/401-handling-distinguishes-stale-responses","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Sign-in refusals for an old credential are now ignored\n\nWhen a server rejects a request because an old credential was used, Claude Code now skips its refusal and retry handling\n\n**What**\n\nA 401 response is the server saying a request was not authorized. Claude Code used to sort every 401 into one of two kinds, withheld or refused. It now checks each 401 more closely. When the 401 is \"stale\", meaning it was about a credential that is no longer the current one, Claude Code no longer treats it as a refusal and does not retry.\n\nClaude Code also now keeps track of whether a request was answered using a sign-in token.\n\n**Why**\n\nThis changes how Claude Code reacts to sign-in failures after you sign in again. A late rejection for a credential you have already replaced should no longer set off the refusal path.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}