{"version":"2.1.286","anchor":"relevant-memory-attachments-no-longer-recorded-as-memory-rea","canonical_anchor":"relevant-memory-attachments-no-longer-recorded-as-memory-rea","heading":"Pinned auto-memory entries are now treated as ordinary auto-memory","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/relevant-memory-attachments-no-longer-recorded-as-memory-rea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Pinned auto-memory entries are now treated as ordinary auto-memory\n\nThe separate AutoMemPinned memory type now becomes AutoMem, its own label is gone, and relevant memories are no longer logged as reads\n\n**Unclear.** Whether this removes read tracking or only moves it elsewhere is not clear.\n\n**What**\n\nAuto-memory is the notes Claude Code saves on its own so it remembers things across conversations. There was a separate \"pinned\" kind, `AutoMemPinned`, that is now merged into ordinary `AutoMem`.\n\n- Saved memory records of type `AutoMemPinned` are now read as `AutoMem`. A record that cannot be read still becomes `User`.\n\n- The separate `AutoMemPinned` case is gone from the memory-source labels. Only `AutoMem` maps to \"user's auto-memory, persists across conversations\".\n\n- The memory file list no longer filters out `AutoMemPinned` entries.\n\n- When relevant memories are attached to a conversation (`relevant_memories`), they are no longer also recorded as memory reads.\n\n**Why**\n\nPinned auto-memory entries now appear and behave like any other auto-memory entry, including in the memory list.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}