{"version":"2.1.284","anchor":"recalled-memory-file-content-is-sanitized-before-injection","canonical_anchor":"recalled-memory-file-content-is-sanitized-before-injection","heading":"Recalled memory files are cleaned before Claude reads them","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/recalled-memory-file-content-is-sanitized-before-injection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Recalled memory files are cleaned before Claude reads them\n\nA memory file's content now goes through the same cleaning step used when memories are written before it is added to Claude's context\n\n**Unclear.** What the cleaning step removes or changes is not clear.\n\n**What**\n\nMemory files hold notes Claude Code keeps for later. When one is recalled, its content was previously added to Claude's context (the text the model sees) exactly as written. It now goes through the same cleaning step used for memory content first. If cleaning changes anything, a line limit is applied. The file path shown in the note saying a memory file was truncated is also cleaned.\n\n**Why**\n\nMemory already had a check on what gets written to it. This adds a matching step when memory is read back, so files that existed before that check are covered too.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}