{"version":"2.1.273","anchor":"session-create-errors-get-a-dedicated-401-message-pointing-a","canonical_anchor":"401-responses-now-suggest-login","heading":"401 errors now point users to \/login","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/session-create-errors-get-a-dedicated-401-message-pointing-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### 401 errors now point users to \/login\n\nAuthentication failures (HTTP 401) now show a message telling you to run \/login\n\n**What** When a request fails with an HTTP 401 (unauthorized), Claude Code now shows a specific message ending in \"\u00b7 Run \/login, then try again\", using a default reason of \"Claude login not accepted\" when no more specific reason is available. This applies generally, and specifically to session-create failures (creating a remote\/teleport session), where a 401 now surfaces this message ahead of the generic fallback error text.\n\n**Why** Previously a 401 could surface a generic or raw server error, leaving it unclear what to do. Pointing directly at `\/login` gives a clear next step when authentication has failed or expired.\n\n- Area: Auth\n- Names: `\/login`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}