Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.224 ·

Read-only memory stores are refused up front

Saving to a read-only memory store now fails immediately and lists stores you can write to.

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

Saving to a memory store that is read-only in the current session now fails immediately with the reason read_only and a list of the stores you can write to, instead of appearing to succeed and not persisting.

Details
  • The system prompt describing the memory index now names the store that owns each entry and marks read-only indexes.
  • Only reached when connected memory stores are in play; which flag enables those is not settled by anything in this build.
Evidence

is read-only in this session; changes will not persist.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.224 →

Feedback