{"version":"2.1.295","anchor":"memory-context-waits-for-rewound-memory-writes","canonical_anchor":"memory-context-waits-for-rewound-memory-writes","heading":"Memory waits to catch up after a rewind removes a memory write","tier":"notice","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/memory-context-waits-for-rewound-memory-writes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Memory waits to catch up after a rewind removes a memory write\n\nIf a rewind undoes something Claude wrote to memory, Claude Code now waits and re-checks memory before the next turn\n\n**What**\n\nRewinding takes a conversation back to an earlier point. Claude can also write notes to memory that are added to each turn. Before each turn, Claude Code already waited for memory to be ready when a stale notice was due. It now also waits when a rewind removed something written to memory, and in some sessions it runs a second check.\n\n**Why**\n\nAfter you rewind past a memory write, the memory Claude sees should no longer include what was undone.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}