{"version":"2.1.283","anchor":"settings-writes-refused-when-the-managed-settings-drop-in-fo","canonical_anchor":"settings-writes-refused-when-the-managed-settings-drop-in-fo","heading":"Settings edits are refused when the managed settings folder cannot be found","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/settings-writes-refused-when-the-managed-settings-drop-in-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Settings edits are refused when the managed settings folder cannot be found\n\nClaude Code now refuses to write a settings file if it cannot locate the managed settings folder to rule it out\n\n**What**\n\nManaged settings are settings an organization installs centrally, including files placed in a drop-in folder. When Claude Code checks whether a file it is about to edit is a settings file, it now also counts files inside those drop-in folders.\n\nIf a drop-in folder's location cannot be worked out, Claude Code cannot rule out that the file is a managed settings file. It then refuses the edit and tells the model not to try again. The check for whether policy covers a path also fails safe: it now needs every drop-in folder to be both resolved and located.\n\n**Why**\n\nThis stops Claude Code from writing into centrally managed policy files. On machines where that folder cannot be resolved, some settings edits may now be refused.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}