{"version":"2.1.290","anchor":"compaction-carries-the-task-list-across","canonical_anchor":"task-list-survives-compaction-rebuild-from-the-compaction-m","heading":"The task list is now carried across compaction","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/compaction-carries-the-task-list-across","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### The task list is now carried across compaction\n\nCompaction now saves a snapshot of the task list, and restoring a session rebuilds tasks from that snapshot so earlier tasks are less likely to vanish\n\n**Unclear.** A condition decides whether this runs, and what that condition is was not settled.\n\n**What**\n\nCompaction is when Claude Code shortens a long conversation by summarising earlier parts so it fits in the model's memory. The task list is the to-do list Claude keeps while it works. Before, the task list was rebuilt only from the task calls left in the conversation, so tasks from before a compaction could be lost.\n\n- Saving: during compaction, a snapshot of the task list is stored with the compaction record (`preCompactTaskList`). If the snapshot is too large, task descriptions are dropped first and then tasks themselves.\n\n- Restoring: the list is rebuilt from that saved snapshot, the rows kept alongside it, and any task calls made after the compaction.\n\n- Safety check: if a task created after the compaction gets an id no higher than one already given out, the id counter has restarted. In that case the saved list is dropped and a debug note explains why.\n\n**Why**\n\nTasks created before a compaction are now much less likely to disappear, including after you resume a session.\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}