{"version":"2.1.323","anchor":"gateway-sign-in-can-be-restored-from-a-login-in-another-ter","canonical_anchor":"gateway-sign-in-can-be-restored-from-a-login-in-another-ter","heading":"A gateway sign-in from another terminal now fixes an expired session","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/gateway-sign-in-can-be-restored-from-a-login-in-another-ter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A gateway sign-in from another terminal now fixes an expired session\n\nWith an enterprise gateway, an expired session can now pick up the sign-in from a `\/login` in another terminal, without a restart\n\n**What**\n\nSome 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.\n\nIf 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.\n\n**Why**\n\nIf 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.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CODE_USE_GATEWAY`, `\/login`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}