{"version":"2.1.286","anchor":"nested-memory-directory-discovery-is-worktree-aware","canonical_anchor":"nested-memory-directory-discovery-is-worktree-aware","heading":"Nested CLAUDE.md and rule lookup understands git worktrees","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/nested-memory-directory-discovery-is-worktree-aware","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Nested CLAUDE.md and rule lookup understands git worktrees\n\nClaude Code's search for nested memory folders now handles git worktrees and no longer mistakes similarly named folders for subfolders\n\n**What**\n\nClaude Code looks through subfolders of your project for nested memory files such as `CLAUDE.md` and rules. That search now understands git worktrees. A worktree is a second working folder linked to the same git repository, often used to work on another branch side by side.\n\n- It works out when you are inside a worktree and maps paths between the worktree and the main checkout.\n\n- It checks folder boundaries properly, so a folder such as `\/foo\/bar2` is no longer treated as being inside `\/foo\/bar`.\n\n**Why**\n\nNested `CLAUDE.md` files and rules should be found correctly when you work from a worktree, and a folder whose name merely starts the same way as your project no longer gets swept in.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}