{"version":"2.1.319","anchor":"cowork-memory-context-is-withheld-for-spawned-loops","canonical_anchor":"cowork-memory-context-is-withheld-for-spawned-loops","heading":"Cowork memory may be kept for spawned loops instead of withdrawn","tier":"internal","area":"Cowork","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/cowork-memory-context-is-withheld-for-spawned-loops","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Cowork memory may be kept for spawned loops instead of withdrawn\n\nWhen there is no memory to serve a spawned loop, Cowork may now keep the existing memory context instead of withdrawing it\n\n**Unclear.** What a user sees differently in a spawned loop is not clear.\n\n**What**\n\nWhen a spawned loop has no memory to be given, Claude Code no longer simply sends a notice that the memory has been withdrawn. A spawned loop is a session started from another session. Claude Code may now keep the current version of the memory context in place.\n\n**Why**\n\nThis changes when memory is taken away from spawned sessions.\n\n- Area: Cowork\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}