{"version":"2.1.301","anchor":"managed-and-user-claudemd-loading-restructured","canonical_anchor":"managed-and-user-claudemd-loading-restructured","heading":"Managed and user CLAUDE.md files are now loaded only under certain conditions","tier":"notice","area":"Memory","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/managed-and-user-claudemd-loading-restructured","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Managed and user CLAUDE.md files are now loaded only under certain conditions\n\nThe managed CLAUDE.md is no longer always loaded, and the user CLAUDE.md now also needs a user file path to exist\n\n**Unclear.** The condition that now skips the managed CLAUDE.md is not known.\n\n**What**\n\nCLAUDE.md files are instruction files Claude Code reads into each conversation. Two of them now load under new conditions:\n\n- The managed CLAUDE.md, set by an organisation, was always loaded before. It is now skipped when a certain internal condition holds.\n\n- The user CLAUDE.md still needs the user settings source to be enabled, and now also needs a user file path to exist.\n\nSetting `CLAUDE_CODE_DISABLE_CLAUDE_MDS` still stops every CLAUDE.md file from loading.\n\n**Why**\n\nIn some situations Claude may not see the managed CLAUDE.md, where before it always did.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: both\n- Heads-up: yes"}