{"version":"2.1.305","anchor":"compaction-telemetry-head-dropped-path-and-ptlattempts","canonical_anchor":"compaction-telemetry-head-dropped-path-and-ptlattempts","heading":"Compaction records more about its summaries and about dropped history","tier":"internal","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/compaction-telemetry-head-dropped-path-and-ptlattempts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Compaction records more about its summaries and about dropped history\n\nConversation compaction now records retries on too-long prompts, dropped history and whether the summary reply was complete\n\n**What**\n\nCompaction is when Claude Code summarizes and shortens a long conversation to free up space. It now records more about how that went.\n\n- The full compaction path now reports its result, including the reply, `outputTokens` (how much text was produced) and `stopReason` (why the reply ended).\n\n- A new `ptlAttempts` count is recorded. When it is above 0, the summary is built with `headTruncated`, meaning the start of the conversation was cut. A compaction that had to drop the start is recorded as `compact_head_dropped`.\n\n- The partial compaction path now records whether the summary block was closed, open or absent, whether an unanswered user request was left after the compacted messages (`prompt`, `other_message` or `none`), and the output tokens and stop reason.\n\nNothing has been read about the gates these run behind.\n\n**Why**\n\nThese are diagnostics rather than new behaviour. One part is visible in practice: when a compaction has to retry and cut the start of a conversation, the summary is now built knowing that the start was dropped.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}