{"version":"2.1.304","anchor":"managed-settings-folder-not-read-when-session-takes-settings","canonical_anchor":"managed-settings-folder-not-read-when-session-takes-settings","heading":"Managed folder on disk is skipped when settings come from your organization","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/managed-settings-folder-not-read-when-session-takes-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Managed folder on disk is skipped when settings come from your organization\n\nWhen a session gets its managed settings from its organization, Claude Code may skip the local managed folder of agents and skills\n\n**Unclear.** Which mode is exempt from this skip, and so which sessions still read the managed folder, is not stated.\n\n**What**\n\nManaged settings are rules set by an organization's administrator. Claude Code can also read a managed folder on disk that holds agents and skills (ready-made helpers and instructions).\n\nWhen a session takes its managed settings from its organization, Claude Code may now skip that folder. It writes a log message explaining that the session's own account could have written to the folder. This does not happen in one particular mode.\n\n**Why**\n\nIf your own account can change the managed folder, its contents cannot be trusted as coming from your organization. Agents or skills you placed there yourself may no longer load in these sessions.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}