{"version":"2.1.219","anchor":"rewritten-memory-system-prompt","canonical_anchor":"rewritten-memory-system-prompt","heading":"Rewritten memory system prompt","tier":"soon","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/rewritten-memory-system-prompt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Rewritten memory system prompt\n\nRewritten memory rules would make Claude save corrections and environment quirks immediately, before replying.\n\n**What**\n\nThe memory instructions given to Claude were rewritten around three criteria and now specify when a memory must be written rather than leaving it to judgement.\n\n**Details**\n\n- Criteria are applicable, durable, legible\n- Explicit MUST-save triggers: user corrections however phrased, skeptical questions, environment discoveries\n- New rule that memory writes happen before the reply that engages the correction, not after the conversation settles\n- The frontmatter template now includes a `metadata: pinned:` field\n- Gated on `tengu_stone_shell`, fallback false\n\n**Evidence**\n\n`A good memory is applicable, durable, and legible`\n\n- Flag `tengu_stone_shell`: Off in both readings (read for one account on one subscription tier against v2.1.219; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Memory\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}