{"version":"2.1.283","anchor":"background-memory-extraction-now-tells-the-main-conversation","canonical_anchor":"background-memory-extraction-now-tells-the-main-conversation","heading":"Claude is told which memory files a background save just wrote","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/background-memory-extraction-now-tells-the-main-conversation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Claude is told which memory files a background save just wrote\n\nWhen background memory saving writes files, the main conversation is told which ones changed so it rereads them instead of using an old copy\n\n**Unclear.** It is not clear whether background memory saving is switched on for every user.\n\n**What**\n\nClaude Code can save memories in the background. A separate pass looks over the conversation and writes notes to memory files on disk. When that pass writes files, it now leaves a notice for the main conversation, summarised as \"saved N memories\" or \"updated the memory index\". The memory index is the file that lists your memories.\n\n- Each file the pass wrote is also refreshed in the main conversation's record of which files it has already read.\n\n- If the pass fails partway through, the notice is still sent for the files it managed to write before the error.\n\nIn the previous build, the background pass left no notice at all.\n\n**Why**\n\nClaude may already have a memory file loaded from earlier in the conversation. The notice tells it that this copy no longer matches what is on disk and that it should read the file again. That stops Claude from editing a memory file based on an out-of-date copy.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}