{"version":"2.1.319","anchor":"oauth-401-recovery-can-skip-refresh","canonical_anchor":"oauth-401-recovery-can-skip-refresh","heading":"Sign-in recovery after a 401 error can now skip the token refresh","tier":"internal","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/oauth-401-recovery-can-skip-refresh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Sign-in recovery after a 401 error can now skip the token refresh\n\nWhen a request fails with a 401 error, Claude Code can now stop before refreshing the sign-in token, and some cloud-session calls keep their token\n\n**Unclear.** Which requests skip the token refresh after a 401 is not known.\n\n**What**\n\nA 401 is the error a server returns when it rejects your sign-in. Claude Code usually reacts by refreshing your sign-in token, the credential that proves who you are. That handling now has an option to stop before the refresh is tried.\n\nWhen a host program manages your sessions, cloud-sessions calls now keep the sign-in token, and a 401 there is taken as that token's own. Before, the host's answer for the sign-in token was cleared.\n\n**Why**\n\nThis changes how sign-in errors are recovered when sessions are managed by a host program.\n\n- Area: Auth\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}