If your API gateway changes during login, the session stops with an explanation instead of half-working.
What's wrong with this entry?
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.
- 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."
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.248
Fast mode credit message no longer points at an unreachable screen
Both mention usage credit
-
v2.1.225
Untrusted-device recovery can be turned off by a flag; unarchive gets its own 403 handling
Both mention login auth
-
v2.1.234
Clearer error when an Anthropic profile login has expired
Both mention login auth