{"version":"2.1.285","anchor":"provider-not-allowed-startup-refusal","canonical_anchor":"provider-not-allowed-startup-refusal","heading":"Admins can restrict which API providers Claude Code may use","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/provider-not-allowed-startup-refusal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Admins can restrict which API providers Claude Code may use\n\nClaude Code can refuse to start with `provider_not_allowed` when managed settings limit providers with `allowedProviders`\n\n**Unclear.** Only the description of this refusal reason was seen, not the code that enforces it.\n\n**What**\n\nThe list of reasons Claude Code can give for refusing to start now includes `provider_not_allowed`. It applies when managed settings (settings an administrator sets for a machine) list the API providers allowed in `allowedProviders`, and the session uses a provider not on that list. An API provider is the service Claude Code sends its requests to.\n\n**Why**\n\nAdministrators get control over which API providers Claude Code may use on a machine.\n\n- Area: Managed Settings\n- Names: `allowedProviders`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}