{"version":"2.1.302","anchor":"managed-settings-files-read-through-a-transform-hook-and-bas","canonical_anchor":"managed-settings-files-read-through-a-transform-hook-and-bas","heading":"Managed settings files are now read through a shared routine","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/managed-settings-files-read-through-a-transform-hook-and-bas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Managed settings files are now read through a shared routine\n\nClaude Code reorganized how it reads `managed-settings.json` and the `managed-settings.d` folder, with no change to what you see\n\n**What**\n\nManaged settings are settings that an organization's administrators enforce on Claude Code. They live in a `managed-settings.json` file and a `managed-settings.d` folder. Claude Code used to read them with code tied to those two locations. It now reads them through a more general routine that can start from settings already loaded and adjust each file as it goes. Error messages, such as `managed-settings.d read failed:`, now name the file through that same routine.\n\n**Why**\n\nThis is internal groundwork for applying organization policy changes during a session. It does not change anything you see.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}