{"version":"2.1.283","anchor":"background-memory-passes-re-sync-read-state-and-notify-the-m","canonical_anchor":"background-memory-passes-re-sync-read-state-and-notify-the-m","heading":"Claude is told when a background memory update rewrites a memory file","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/background-memory-passes-re-sync-read-state-and-notify-the-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Claude is told when a background memory update rewrites a memory file\n\nAfter a background memory pass writes memory files, Claude Code refreshes what it knows about them and tells Claude which ones changed\n\n**Unclear.** Which background passes use this, and whether the memory features involved are switched off by default, are not settled.\n\n**What**\n\nClaude Code can keep memory files, notes it carries between conversations, and can update them in the background. When a background pass writes memory files, Claude Code now refreshes its record of each file as last read, and logs whether the content changed or only the file's timestamp did. The files it can locate are then listed in the existing memory-update notice sent to Claude. Files it cannot locate are left out of the notice.\n\n**Why**\n\nThis should stop errors about a file having changed since it was read when Claude edits a memory file that a background pass has just rewritten.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}