{"version":"2.1.311","anchor":"cloud-gateway-allowedproviders-check-restructured","canonical_anchor":"cloud-gateway-allowedproviders-check-restructured","heading":"Check that blocks claude gateway under provider restrictions was rewritten","tier":"internal","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/cloud-gateway-allowedproviders-check-restructured","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Check that blocks `claude gateway` under provider restrictions was rewritten\n\nThe check that stops `claude gateway` when managed settings restrict API providers was rewritten; its message is unchanged\n\n**Unclear.** It is not clear whether the rewritten check blocks `claude gateway` in the same cases as the old one.\n\n**What**\n\nManaged settings are settings an organisation's administrator controls. One of them, `allowedProviders`, limits which API providers a machine may use. When it is set, Claude Code refuses to run the Cloud gateway server through `claude gateway`, because that server's upstreams are configured outside the policy.\n\nThe check that makes this decision was rewritten and now returns its answer explicitly. The message you see when blocked is the same as before.\n\n**Why**\n\nIf your organisation uses `allowedProviders`, this is the check that decides whether `claude gateway` starts. Watch whether it still allows and blocks the same machines as before.\n\n- Area: Gateway\n- Names: `allowedProviders`, `claude gateway`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}