You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ElsewhereArea: what it touches
Bug FixesKind: in v2.1.323,
Bug FixesSection of the release
What
Some organisations route Claude Code through an enterprise gateway, a company server that sits between Claude Code and the API, turned on with CLAUDE_CODE_USE_GATEWAY. When a session's gateway sign-in expires, Claude Code now checks the stored credentials for a newer sign-in, such as one made with /login in another terminal window. It uses that sign-in if the gateway, the account and the kind of sign-in all match.
If no match is found, the session stays expired until you run /login in it or restart. Claude Code also now logs why a stored sign-in was or was not used. When renewing, it refuses the stored sign-in if a secure connection check to the gateway fails.
Why
If you use an enterprise gateway, signing in again in one terminal can now restore your other sessions, so you no longer have to restart them.
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed sessions that kept failing after a Claude apps gateway sign-in expired: once you sign in again with /login in another terminal, they…
