{"version":"2.1.285","anchor":"memory-extraction-prompt-no-longer-varies-by-a-gate","canonical_anchor":"memory-extraction-prompt-no-longer-varies-by-a-gate","heading":"Instructions for saving memories no longer vary","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/memory-extraction-prompt-no-longer-varies-by-a-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Instructions for saving memories no longer vary\n\nClaude now always gets the same instruction for saving memories: save as whichever type fits best, following the memory type and what-not-to-save rules\n\n**What**\n\nClaude Code can save memories, notes kept for later sessions. The instruction Claude gets about saving them no longer switches between two versions. It now always says that when you explicitly ask it to remember something, it should save it as whichever type fits best. It should also follow the rules on memory types and on what not to save. The other version, which said to save it immediately and follow separate memory-writing guidance, is gone.\n\n**Why**\n\nEveryone now gets the same memory instruction, the older of the two versions.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}