{"version":"2.1.227","anchor":"memory-files-are-tracked-by-how-they-entered-the-session","canonical_anchor":"memory-files-are-tracked-by-how-they-entered-the-session","heading":"Memory files are tracked by how they entered the session","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/memory-files-are-tracked-by-how-they-entered-the-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Memory files are tracked by how they entered the session\n\nClaude Code now tracks how each memory file reached the session and whether it was used.\n\n**What**\n\nNew bookkeeping records how each memory file arrived (in the prompt body, surfaced, merely listed, or not at all) and whether it was later read, written, or both, then matches a memory the model names against that set. It exists to judge whether a cited memory was actually available; nothing new is shown to you.\n\n**Evidence**\n\n`read_written`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}