{"version":"2.1.295","anchor":"enterprise-gateway-refresh-token-write-no-longer-creates-a-m","canonical_anchor":"enterprise-gateway-refresh-token-write-no-longer-creates-a-m","heading":"Saving an enterprise gateway login token no longer recreates a removed entry","tier":"notice","area":"Elsewhere","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/enterprise-gateway-refresh-token-write-no-longer-creates-a-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Saving an enterprise gateway login token no longer recreates a removed entry\n\nClaude Code no longer recreates a missing enterprise gateway entry when saving a refresh token, and keeps a stored one that differs\n\n**What**\n\nAn enterprise gateway is a company-run service that sits between Claude Code and the model. Claude Code keeps a refresh token for it, which lets it renew your login without asking again. When saving that token:\n\n- If there is no gateway entry in your configuration, Claude Code now leaves the configuration alone. Before, it built a new entry from the current session.\n\n- If the stored token is not the one expected, Claude Code keeps the stored entry instead of overwriting it.\n\n**Why**\n\nThis appears to stop a gateway login from being written back after you have logged out or changed gateway.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}