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

Claude Code v2.1.242 ·

Memory writes into read-only stores say plainly that nothing was shared

Writes into read-only memory stores now warn they were saved locally only and will be overwritten.

Use it now Notable No documentation found New Features
JSON All of v2.1.242
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
MemoryArea: what it touches
New FeaturesKind: in v2.1.242,
What probably matters to youSection of the release
What

Writing to a file under a memory store mounted read-only now returns a notice that the write was saved locally only, will not sync, and will be overwritten by the next pull, along with a remedy naming the writable stores to use instead. A per-turn scan also lists files that exist only on this machine and tells the model to correct the user if it claimed the content was saved. Set CLAUDE_CODE_DISABLE_MEMORY_RO_UNSAVED_NOTICE to turn the scan off.

Details
  • The remedy line is computed from the stores that are actually writable, not a fixed string.
  • The per-turn summary is queued as context for the model, so the correction happens in the conversation rather than only in tool output.
Evidence

This file's memory store is mounted read-only: writes are never synced, and the next sync pull will overwrite local edits with server content. This write was saved locally only and is NOT in shared memory.

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

Read from
How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: CLAUDE_CODE_DISABLE_MEMORY_RO_UNSAVED_NOTICE

See this entry in the whole of v2.1.242 →

Feedback