{"version":"2.1.288","anchor":"compaction-can-reuse-a-prior-summary-coverage-check","canonical_anchor":"compaction-can-reuse-a-prior-summary-coverage-check","heading":"Compaction can reuse a summary it already made","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/compaction-can-reuse-a-prior-summary-coverage-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Compaction can reuse a summary it already made\n\nClaude Code can decide to reuse an earlier compaction summary, and refuses when, for example, the result would not fit\n\n**Unclear.** What triggers this reuse, and whether it is switched on, is not stated.\n\n**What**\n\nCompaction is how Claude Code shortens a long conversation by replacing older messages with a summary. Claude Code now has logic that decides whether a summary it already made can be reused. It refuses in cases such as these:\n\n- the marker for where the summary starts is missing\n\n- there is a reply the summary has not seen\n\n- a hook rewrote the messages (a hook is a script you set up to run at certain moments)\n\n- the result would not fit\n\n**Why**\n\nReusing an existing summary could make compaction quicker.\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}