{"version":"2.1.317","anchor":"401-handling-honors-route-owned-answers","canonical_anchor":"401-handling-honors-route-owned-answers","heading":"Fewer needless login refreshes after some \"not authorised\" replies","tier":"notice","area":"Auth","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/401-handling-honors-route-owned-answers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Fewer needless login refreshes after some \"not authorised\" replies\n\nClaude Code now skips refreshing your login after a \"not authorised\" reply when that reply belongs to the request itself\n\n**What**\n\nA 401 is a server reply meaning \"not authorised\". Claude Code usually reacts by refreshing your login and trying again. It now skips that step in more cases where the reply is the request's own answer rather than a problem with your login, judged from both the reply and its headers. Before, only the reply itself was checked.\n\n**Why**\n\nThis avoids refreshing your login when nothing is wrong with it.\n\n- Area: Auth\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}