{"version":"2.1.224","anchor":"memory-extraction-can-be-told-to-save-only-personal-memories","canonical_anchor":"memory-extraction-can-be-told-to-save-only-personal-memories","heading":"Memory extraction can be told to save only personal memories","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/memory-extraction-can-be-told-to-save-only-personal-memories","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Memory extraction can be told to save only personal memories\n\nMemory extraction can be told to save only personal memories, with nothing visibly setting that mode.\n\n**What**\n\nThe memory-extraction prompt has a new mode that tells the model the project-shared memory tools are unavailable and that only personal-directory memories should be saved. It is switched by a flag passed in by the caller, and nothing in this build shows what sets that flag.\n\n**Details**\n\n- Related team-memory prompts dropped the branch saying a private directory would still persist.\n- The memory upkeep prompt can now skip its \"Read the index\" step.\n\n**Evidence**\n\n`so skip anything the scope guidance marks as shared with the project`\n\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}