Claude Code v2.1.301 ·
Managed and user CLAUDE.md files are now loaded only under certain conditions
The managed CLAUDE.md is no longer always loaded, and the user CLAUDE.md now also needs a user file path to exist
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.301,
ImprovementsSection of the release
Unclear The condition that now skips the managed CLAUDE.md is not known.
What
CLAUDE.md files are instruction files Claude Code reads into each conversation. Two of them now load under new conditions:
- The managed CLAUDE.md, set by an organisation, was always loaded before. It is now skipped when a certain internal condition holds.
- The user CLAUDE.md still needs the user settings source to be enabled, and now also needs a user file path to exist.
Setting CLAUDE_CODE_DISABLE_CLAUDE_MDS still stops every CLAUDE.md file from loading.
Why
In some situations Claude may not see the managed CLAUDE.md, where before it always did.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe condition that now skips the managed CLAUDE.md is not known.
See this entry in the whole of v2.1.301 →
