{"version":"2.1.246","anchor":"an-empty-managed-settings-tier-can-come-from-a-host-attestat","canonical_anchor":"an-empty-managed-settings-tier-can-come-from-a-host-attestat","heading":"An empty managed-settings tier can come from a host attestation","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/an-empty-managed-settings-tier-can-come-from-a-host-attestat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### An empty managed-settings tier can come from a host attestation\n\nClaude Code can skip reading policy settings from disk when the host says there are none.\n\n**What**\n\nWhen the storage backend attests the machine has no OS policy folder, the settings walk is handed an empty managed-settings tier without touching disk. If `CLAUDE_CODE_MANAGED_SETTINGS_PATH` was set explicitly, that contradiction is recorded and the walk reads the files itself.\n\n**Evidence**\n\n`settingsPrime: the host attests this machine has no OS policy folder ('system' absent); the policy walk is served an empty managed-settings file tier without reading the host`\n\n- Area: Settings\n- Names: `CLAUDE_CODE_MANAGED_SETTINGS_PATH`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}