You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Managed SettingsArea: what it touches
ImprovementsKind: in v2.1.304,
ImprovementsSection of the release
Unclear Which accounts and plans the server applies this check to is not known.
What
Organizations can set rules and limits for Claude Code that it fetches at startup. Claude Code now has a check that looks at whether those fetches worked and decides one of these:
pass
pass using a stored earlier result
pass because the account is exempt
blocked
refused
When blocked, Claude Code shows a message such as "Claude Code couldn't load your organization's settings, which it requires before a session can start." In the interactive screen you get a blocked screen with a retry option. Headless runs, where Claude Code runs without its interactive screen, exit with the message.
The check is controlled by a setting Claude Code reads from the server. That setting can give a time limit, a share of accounts, which plans it covers, and a grace period in hours.
Why
For team and enterprise accounts where it applies, a failure to load organization settings can now stop a session from starting at all, rather than letting it run without them.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhich accounts and plans the server applies this check to is not known.
