{"version":"2.1.90","anchor":"memory-system-refinements","canonical_anchor":"memory-system-refinements","heading":"Memory System Refinements","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.90\/e\/memory-system-refinements","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.90","markdown":"### Memory System Refinements\n\n- The two-step memory save process (write file, then update MEMORY.md index) has been simplified \u2014 the MEMORY.md index step has been removed, and memory is saved directly to individual files. The number of `MEMORY.md` references decreased from 10 to 6 between versions.\n- Memory retrieval now prefixes content with \"Retrieved for possible relevance \u2014 use only if it actually applies to what the user asked\" to reduce false positive influence.\n- Memory selection is now more conservative with user-profile and project-overview memories: the system explicitly avoids matching on surface keyword overlap (e.g., a profile mentioning \"DB performance\" won't be selected just because a question contains the word \"performance\").\n- Memory extraction now skips runs where no user prose has been added since the last extraction, reducing unnecessary extraction cycles (search for `\"[extractMemories] skipping \u2014 no user prose since last extraction\"`).\n- The extraction prompt now includes \"If nothing is worth saving, output only 'Nothing to save.' Do not explain why.\" for cleaner no-op results.\n\n**Evidence**\n\nMemory selection system prompt (search for `\"Be especially conservative with user-profile\"`) and extraction guard (search for `\"no user prose since last extraction\"`)"}