You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
AuthArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What
When a machine's managed settings (an admin-controlled settings file) require signing in through a cloud gateway, Claude Code used to show the raw internal error "forceLoginMethod is 'gateway' in managed settings". It now shows a plain-language message instead: managed settings on this machine configure a cloud gateway sign-in, and the user should run /login from an interactive terminal to authenticate. This applies both to the CLI's login-validation path and to a separate stderr early-exit path.
Why
The old message exposed an internal setting name that meant nothing to most users. The new wording tells people what's actually happening and what to do about it.
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.
Added sinceA small documentation edit on Claude Code on Claude Platform on AWS touched a line naming /login after this was published.The `/login` and `/logout` commands don't sign you into a claude.ai subscription for Claude Platform on AWS. Authentication runs through your AWS credentials or workspace API key.claude-platform-on-awssee the edit
Confirmed sinceAnthropic's documentation has since written up /login, on Claude Code changelog.* Added the `gatewayInternalNetworks` managed setting, letting administrators allow `/login` to a Claude apps gateway on their organization's own public IPv4 blockchangelogsee the edit
How sure we are
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /login, on Claude Code changelog.
Anthropic's release notes agreeFixed /login showing "no gateway URL is configured" when re-run in a session that signed in to a Claude apps gateway set by managed settings
