{"version":"2.1.172","anchor":"team-memory-two-step-save-process-instructions","canonical_anchor":"team-memory-two-step-save-process-instructions","heading":"Team Memory: Two-Step Save Process Instructions","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.172\/e\/team-memory-two-step-save-process-instructions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.172","markdown":"### Team Memory: Two-Step Save Process Instructions\n\n**What**\n\nThe team memory system prompt has been overhauled with clearer, step-by-step guidance for saving memories. When using indexed memory, the instructions now explicitly describe a two-step process (write the memory file, then add a pointer to the index).\n\n**Details**\n\n- Step 1: Write memory to its own file using the frontmatter format\n- Step 2: Add a pointer entry (`- [Title](file.md) \u2014 one-line hook`) to the index file\n- Index entries are capped at ~150 characters\n- Clarified that team memory directories already exist \u2014 no need to run `mkdir`\n- Read-only sessions now receive: \"If the user asks you to remember something, explain that memory is read-only in this session.\"\n\n**Evidence**\n\nNew team memory prompt builder (search for `\"**Step 1** \u2014 write the memory to its own file in\"`)"}