{"version":"2.1.292","anchor":"rewind-to-summary-telemetry-records-kept-rows","canonical_anchor":"rewind-to-summary-telemetry-records-kept-rows","heading":"Compaction now records how many rows were kept after a summary","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/rewind-to-summary-telemetry-records-kept-rows","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Compaction now records how many rows were kept after a summary\n\nThe compaction result now stores keptRows with its after_summary marker, and rewinding to a summary reports that count\n\n**What**\n\nCompaction is when Claude Code replaces older parts of a long conversation with a summary. The compaction result marks where the summary sits with a resolution of `after_summary`.\n\n- That marker is now set together with `keptRows`, the number of rows of conversation kept after the summary. It is set whenever the relevant cut point exists. Before, the marker was set under a different condition and carried no `keptRows`.\n\n- When you rewind to a point inside summarized history, the usage record sent for that rewind now includes `kept_rows` (`e.cut.keptRows ?? 0`). Before, it carried no details.\n\n**Why**\n\nThe compaction change can affect how a session picks up again after it was compacted. The rewind change only adds a number to the usage data Claude Code reports and does not change what you see.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}