{"version":"2.1.295","anchor":"cloud-gateway-restore-refused-when-org-settings-name-another","canonical_anchor":"cloud-gateway-restore-refused-when-org-settings-name-another","heading":"Saved Cloud gateway is not reconnected if your organization names a different one","tier":"notice","area":"LLM Gateway","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/cloud-gateway-restore-refused-when-org-settings-name-another","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Saved Cloud gateway is not reconnected if your organization names a different one\n\nClaude Code no longer reconnects to a saved Cloud gateway when your organization's settings name another gateway or none\n\n**What**\n\nWhen Claude Code restores a saved Cloud gateway connection, it now checks your organization's settings first. If those settings name a different gateway, or no gateway at all, Claude Code does not connect. It shows a warning saying it is not connected to the Cloud gateway because your organization's settings name another gateway or none.\n\n**Why**\n\nOrganizations that manage their settings centrally get stricter control over which gateway Claude Code uses, and a saved connection can no longer go around that.\n\n- Area: LLM Gateway\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}