{"version":"2.1.232","anchor":"logging-in-can-now-end-the-session-if-the-gateway-changed-un","canonical_anchor":"logging-in-can-now-end-the-session-if-the-gateway-changed-un","heading":"Logging in can now end the session if the gateway changed underneath it","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/logging-in-can-now-end-the-session-if-the-gateway-changed-un","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Logging in can now end the session if the gateway changed underneath it\n\nIf your API gateway changes during login, the session stops with an explanation instead of half-working.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- The login flow now compares against the gateway auth state captured before login and returns either a gateway login error or a relaunch result.\n- The final message includes the line \"This session is ending so that nothing from that gateway stays half-applied.\"\n\n**Evidence**\n\n`This session is ending so that nothing from that gateway stays half-applied.`\n\n- Area: Auth\n- Names: `\/login`, `\/upgrade`, `\/usage-credits`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}