{"version":"2.1.284","anchor":"pausingresuming-memory-now-forces-a-context-re-read-with-a","canonical_anchor":"pausingresuming-memory-now-forces-a-context-re-read-with-a","heading":"Pausing or resuming memory now refreshes what Claude sees in the same session","tier":"notice","area":"Memory","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/pausingresuming-memory-now-forces-a-context-re-read-with-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Pausing or resuming memory now refreshes what Claude sees in the same session\n\nPausing or resuming memory makes Claude Code re-read your memory and instruction files right away, with a note saying why\n\n**Unclear.** It is not clear whether pausing memory previously left out-of-date memory in Claude's context by some other route.\n\n**What**\n\nWhen you pause or resume memory for a session, Claude Code now throws away its saved copy of your memory and instruction files and reads them again. The note that tells Claude its context has changed now gives the reason as memory being paused or resumed for this session.\n\n**Why**\n\nAfter you pause memory, Claude's view of your memory files now updates in the same session instead of waiting for a new one.\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}