{"version":"2.1.288","anchor":"parked-agent-contexts-are-torn-down-when-the-last-keepalive","canonical_anchor":"parked-agent-contexts-are-torn-down-when-the-last-keepalive","heading":"Finished background agents are now cleaned up once nothing needs them","tier":"notice","area":"Background Agents","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/parked-agent-contexts-are-torn-down-when-the-last-keepalive","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Finished background agents are now cleaned up once nothing needs them\n\nWhen the last reason to keep a finished agent around is released, Claude Code now clears its stored context\n\n**Unclear.** It is not clear which kinds of agent tasks this affects.\n\n**What**\n\nClaude Code keeps an agent's task (a helper copy of Claude working on part of a job) available while something still needs it. When the last of these reasons is released, Claude Code now checks whether the task has finished and is not being resumed or wrapped up. If so, it clears the agent's stored conversation and runs its cleanup.\n\nBefore, releasing the last reason only updated the task's records, and no cleanup ran.\n\n**Why**\n\nThis probably stops finished background agents from holding on to memory after they are done.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}