{"version":"2.1.315","anchor":"memory-path-check-short-circuits-unless-the-path-mentions-me","canonical_anchor":"memory-path-check-short-circuits-unless-the-path-mentions-me","heading":"Memory path check now looks for the word \"memory\" first","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/memory-path-check-short-circuits-unless-the-path-mentions-me","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Memory path check now looks for the word \"memory\" first\n\nA check for memory file paths now gives up straight away when the path does not contain the word \"memory\"\n\n**Unclear.** It is unclear whether any memory folder can have a path without the word \"memory\" and so be missed.\n\n**What**\n\nClaude Code has a check that decides whether a file path belongs to its memory files (notes Claude Code keeps and reads back across sessions). That check now stops immediately and answers no when the path does not contain the word \"memory\" anywhere.\n\n**Why**\n\nThis mainly saves work on paths that clearly are not memory files. A memory folder whose path does not include the word \"memory\" would no longer be recognized by this check.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}