{"version":"2.1.242","anchor":"memory-writes-into-read-only-stores-say-plainly-that-nothing","canonical_anchor":"memory-writes-into-read-only-stores-say-plainly-that-nothing","heading":"Memory writes into read-only stores say plainly that nothing was shared","tier":"use","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/memory-writes-into-read-only-stores-say-plainly-that-nothing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Memory writes into read-only stores say plainly that nothing was shared\n\nWrites into read-only memory stores now warn they were saved locally only and will be overwritten.\n\n**What**\n\nWriting 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.\n\n**Details**\n\n- The remedy line is computed from the stores that are actually writable, not a fixed string.\n- The per-turn summary is queued as context for the model, so the correction happens in the conversation rather than only in tool output.\n\n**Evidence**\n\n`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.`\n\n- Area: Memory\n- Names: `CLAUDE_CODE_DISABLE_MEMORY_RO_UNSAVED_NOTICE`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}