{"version":"2.1.224","anchor":"private-memory-directory-dropped-from-the-prompt","canonical_anchor":"private-memory-directory-dropped-from-the-prompt","heading":"Private memory directory dropped from the prompt","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/private-memory-directory-dropped-from-the-prompt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Private memory directory dropped from the prompt\n\nClaude no longer mentions a private memory folder, and team memory is set up purely through the environment.\n\n**What**\n\nClaude no longer describes a separate private memory directory alongside team memory, and the path that discovered and mounted memory stores at runtime is gone. Team memory sync is now configured only through the environment.\n\n**Details**\n\n- All prompt branches mentioning a private memory area were removed; the remaining text states plainly that there is no separate private memory directory in the session.\n- The store picker and its telemetry went with the discovery path; the team memory sync watcher now always reports its config source as env.\n- The memory-type descriptions and the instruction to cite memory with tags moved into shared constants.\n\n**Evidence**\n\n`There is no separate private memory directory in this session.`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}