{"version":"2.1.269","anchor":"new-401-during-token-refresh-error-message","canonical_anchor":"new-401-during-token-refresh-error-message","heading":"New 401-during-token-refresh error message","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-401-during-token-refresh-error-message","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New 401-during-token-refresh error message\n\nA clearer error message now appears when an API request gets a 401 while your login is being refreshed, and Claude Code retries automatically\n\n**What**\n\nIf an API request returns HTTP 401 (unauthorized) at the exact moment Claude Code is refreshing the session's credentials, users now see a specific message explaining that the sign-in was rejected while it was being refreshed, instead of the generic 'rejected credentials' message. Claude Code also now automatically retries the request in this case.\n\n**Why**\n\nThis avoids alarming or confusing generic-looking errors during a normal credential refresh, and the automatic retry means a brief 401 during refresh no longer requires the user to intervene manually.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}