{"version":"2.1.301","anchor":"managed-settings-system-absent-attestation-now-covers-clau","canonical_anchor":"managed-settings-system-absent-attestation-now-covers-clau","heading":"Managed-settings path is no longer read when the host says there are no system settings","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/managed-settings-system-absent-attestation-now-covers-clau","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Managed-settings path is no longer read when the host says there are no system settings\n\nIf the host running Claude Code reports there are no system-wide settings, the folder named by CLAUDE_CODE_MANAGED_SETTINGS_PATH is now skipped too\n\n**What**\n\nManaged settings are settings an organisation puts on a machine to control Claude Code. Some programs that host Claude Code can report that the machine has no system-wide settings at all.\n\nWhen the host reports this, Claude Code now skips both the operating system's policy folder and the folder named by `CLAUDE_CODE_MANAGED_SETTINGS_PATH`. The session then has no managed-settings files. Before, setting `CLAUDE_CODE_MANAGED_SETTINGS_PATH` meant that folder was still read. Sessions without local storage also load no managed-settings files.\n\n**Why**\n\nThis changes which policy settings apply when Claude Code runs inside another program or on a remote host. If you rely on `CLAUDE_CODE_MANAGED_SETTINGS_PATH` in such a setup, it may no longer be read.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}