{"version":"2.1.69","anchor":"memory-system-overhaul","canonical_anchor":"memory-system-overhaul","heading":"Memory System Overhaul","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.69\/e\/memory-system-overhaul","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.69","markdown":"### Memory System Overhaul\n\n**What**\n\nComplete restructuring of the persistent memory system with typed categories, frontmatter format, and two-step save process.\n\n**Details**\n\n- Four memory types: `user` (preferences\/role), `feedback` (corrections\/guidance), `project` (ongoing work context), and `reference` (external system pointers)\n- Memories use markdown files with YAML frontmatter (`name`, `description`, `type` fields)\n- Two-step save: write the memory file, then add a pointer in the memory index\n- Clear guidance on what NOT to save (code patterns, git history, ephemeral details)\n- When users correct information stated from memory, the stored entry must be updated\n- `CLAUDE_COWORK_MEMORY_PATH_OVERRIDE` environment variable to customize the memory directory\n\n**Evidence**\n\nMemory system (search for `\"## Types of memory\"`, `\"## What NOT to save in memory\"`, `\"CLAUDE_COWORK_MEMORY_PATH_OVERRIDE\"`)"}