{"version":"2.1.282","anchor":"memory-file-attachment-sets-a-view-limit-when-an-item-block","canonical_anchor":"memory-file-attachment-sets-a-view-limit-when-an-item-block","heading":"Memory files are marked as partial when part of their content was removed","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/memory-file-attachment-sets-a-view-limit-when-an-item-block","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Memory files are marked as partial when part of their content was removed\n\nA memory file attached to a conversation is now marked as partially shown when part of it was removed, not only when it was too long\n\n**Unclear.** It is unclear what kind of content counts as a removed block in a memory file.\n\n**What**\n\nMemory files are files of notes and instructions that Claude Code attaches to a conversation for the model to read. Claude Code now reads them in a way that can also report that a certain block of content was removed. When that happens, the attached file is marked as only partly shown, the same way it already was when the file was cut short for being too many lines or too large. The wording of the notice about a shortened file has not changed.\n\n**Why**\n\nIn practice, some section of a memory file may now be left out before it reaches the model, and the attachment says so.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}