Follow Discord
Sweep 01 Oct 2026 · 17:27Z Build v2.1.287 508 read Stable v2.1.285 Latest v2.1.287 Next v2.1.287 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.286 ·

Pinned auto-memory entries are now treated as ordinary auto-memory

The separate AutoMemPinned memory type now becomes AutoMem, its own label is gone, and relevant memories are no longer logged as reads

Group of 3 You'll notice Improvements
JSON All of v2.1.286
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
MemoryArea: what it touches
ImprovementsKind: in v2.1.286,
ImprovementsSection of the release

What

Auto-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.

  • Saved memory records of type AutoMemPinned are now read as AutoMem. A record that cannot be read still becomes User.
  • The separate AutoMemPinned case is gone from the memory-source labels. Only AutoMem maps to "user's auto-memory, persists across conversations".
  • The memory file list no longer filters out AutoMemPinned entries.
  • When relevant memories are attached to a conversation (relevant_memories), they are no longer also recorded as memory reads.

Why

Pinned auto-memory entries now appear and behave like any other auto-memory entry, including in the memory list.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhether this removes read tracking or only moves it elsewhere is not clear.

See this entry in the whole of v2.1.286 →

Feedback