{"version":"2.1.293","anchor":"new-startup-refusal-codes-for-required-org-config","canonical_anchor":"new-startup-refusal-codes-for-required-org-config","heading":"Two new reasons for refusing to start when organization settings are required","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/new-startup-refusal-codes-for-required-org-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Two new reasons for refusing to start when organization settings are required\n\nClaude Code can now say it refused to start because required organization settings could not be loaded, or were refused for this sign-in\n\n**What**\n\nSome organizations require their usage limits and managed settings to be in place before a session can start. Claude Code has two new reasons it can give for refusing to start in that case:\n\n- `org_config_required_unavailable`: the settings could not be loaded; trying again may work\n\n- `org_config_refused`: Anthropic refused the settings for this sign-in; signing in again or a change by an administrator is needed\n\n**Why**\n\nA program hosting Claude Code can now tell these organization-settings failures apart from other startup failures and tell you whether to retry or to fix the sign-in.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}