{"version":"2.1.248","anchor":"an-unreadable-managed-settings-drop-in-directory-is-now-a-fa","canonical_anchor":"an-unreadable-managed-settings-drop-in-directory-is-now-a-fa","heading":"An unreadable managed-settings drop-in directory is now a fatal error","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/an-unreadable-managed-settings-drop-in-directory-is-now-a-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### An unreadable managed-settings drop-in directory is now a fatal error\n\nAn unreadable managed-settings drop-in directory now stops Claude Code with a fatal error.\n\n**What**\n\nOn 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.\n\n**Details**\n\n- The error text names the directory that could not be read.\n- Applies to the drop-in directory alongside the main managed settings file.\n\n**Evidence**\n\n`Managed settings drop-in directory could not be read: `\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}