You'll notice
Useful3 Signal2
An unreadable managed-settings drop-in directory now stops Claude Code with a fatal error.
What's wrong with this entry?
Anonymous. No account, no email.
What
On enterprise-managed installs, a managed-settings.d directory that cannot be read used to produce only a log line. It now raises a settings error with severity fatal, so a broken policy directory is surfaced instead of Claude Code carrying on with partial policy.
Details
- The error text names the directory that could not be read.
- Applies to the drop-in directory alongside the main managed settings file.
Evidence
Managed settings drop-in directory could not be read:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Org-anchored consent for remote managed settings
Both mention managed
-
v2.1.224
Consent to dangerous remote settings is remembered per organization
Both mention managed
-
v2.1.228
Managed policy helper failures throw instead of returning text
Both mention managed