What
If the API gateway in force when you logged in no longer matches afterwards, Claude Code stops the session with an explanation instead of carrying on half-configured. /login, /usage-credits and /upgrade all print that message through one shared formatter.
Details
- The login flow now compares against the gateway auth state captured before login and returns either a gateway login error or a relaunch result.
- The final message includes the line "This session is ending so that nothing from that gateway stays half-applied."
Evidence
This session is ending so that nothing from that gateway stays half-applied.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
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.
Confirmed since
Anthropic's documentation has since written up /usage-credits, on Error reference.
* On Pro and Max, increase your monthly spend limit in [**Settings > Usage**](https://claude.ai/settings/usage) on claude.ai, or run `/usage-credits`errors see the edit
Confirmed since
Anthropic'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 blockchangelog see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up /login, on Claude Code changelog.
Anthropic's release notes agree
Fixed Cloud gateway /login exiting silently or leaving an unresponsive terminal after "Press Enter to continue" when managed settings failed…