{"version":"2.1.246","anchor":"memory-writes-outside-the-default-memory-folder-now-ask-firs","canonical_anchor":"memory-writes-outside-the-default-memory-folder-now-ask-firs","heading":"Memory writes outside the default memory folder now ask first","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/memory-writes-outside-the-default-memory-folder-now-ask-firs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Memory writes outside the default memory folder now ask first\n\nMemory saves inside the standard folder skip the prompt; saves outside it always ask you.\n\n**What**\n\nThe memory write tool now separates your personal store from a shared project store. In automatic mode, saving to your personal store inside the standard memory directory goes through without a prompt, where previously every save went to classifier review. A personal save that would land outside that directory now always asks you, and is marked so the automatic classifier cannot approve it on your behalf.\n\n**Details**\n\n- The forced prompt carries a safety-check reason flagged `classifierApprovable: !1`, so only you can allow it.\n- When the classifier is consulted for such a write, its input now names the exact destination path.\n- Results carry a `store_kind` field, and personal content passes through a per-store transform before being written.\n- Reachable wherever the memory tools are enabled; this release does not change that enablement check.\n\n**Evidence**\n\n`outside the memory directory Claude Code saves to without asking`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}