{"version":"2.1.315","anchor":"cowork-memory-context-withdrawn-from-spawned-loops-with-lap","canonical_anchor":"cowork-memory-context-withdrawn-from-spawned-loops-with-lap","heading":"Cowork memory is now withdrawn from spawned loops, with an emergency off","tier":"notice","area":"Cowork","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/cowork-memory-context-withdrawn-from-spawned-loops-with-lap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Cowork memory is now withdrawn from spawned loops, with an emergency off\n\nIn Cowork, Claude Code now sends empty memory to the loops it starts, and a new emergency check can turn memory off on the laptop side\n\n**What**\n\nIn Cowork, Claude can be given saved memory, background information carried from earlier work. Claude Code changes how that memory is handled in three ways:\n\n- Spawned loops: when Claude Code starts a separate working loop, it now sends that loop an empty memory context, which withdraws the memory from it.\n\n- Memory reset: when memory is reset, the versions already handed out are now marked as withdrawn.\n\n- Emergency off: a new check can turn memory off on the laptop side of the session.\n\nBefore, memory could only be withdrawn through an older route, and there was no emergency check.\n\n**Why**\n\nThis keeps out-of-date memory from reaching subagents, which are helper agents Claude starts to handle part of a task.\n\n- Area: Cowork\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: yes"}