{"version":"2.1.287","anchor":"oauth-revoked-detection-also-matches-401","canonical_anchor":"oauth-revoked-detection-also-matches-401","heading":"Claude Code recognises more ways a revoked login is reported","tier":"notice","area":"Sign-In","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/oauth-revoked-detection-also-matches-401","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Claude Code recognises more ways a revoked login is reported\n\nA 401 error saying the OAuth access token has been revoked now counts as a revoked login, as well as the 403 form\n\n**Unclear.** What Claude Code does after it detects a revoked token was not stated.\n\n**What**\n\nClaude Code checks errors from the server to spot when your login token has been revoked. Before, it only matched a 403 error whose message said \"OAuth token has been revoked\". It now also matches a 401 error whose message includes \"OAuth access token has been revoked\".\n\n**Why**\n\nMore cases of a revoked login are now recognised for what they are.\n\n- Area: Sign-In\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}