Authentication failures (HTTP 401) now show a message telling you to run /login
What When a request fails with an HTTP 401 (unauthorized), Claude Code now shows a specific message ending in "· 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.
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.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
| Startup exits with `Administrator policy requires a Cloud gateway sign-in on this machine` | The developer's environment sets `ANTHROPIC_API_KEY` or `ANTHROPIC_AUTH_TOKEN`, their settings configure an [`apiKeyHelper`](/docs/en/settings-r…claude-apps-gateway-deploy see the edit
A sign-in from an earlier version of Claude Code picks up plugin access the next time Claude Code renews that sign-in in the background, within a few hours, or right away if you run `/login` again. Plugin sync starts the next time you star…plugins-reference see the edit
Anthropic's documentation has since written up /login, on Plugins reference.
Fixed 401/403 errors on Bedrock, Vertex and Foundry, and Claude apps gateway 403s, telling you to run /login; the message now names the…