{"version":"2.1.310","anchor":"compact-end-progress-event-held-back-until-compaction-result","canonical_anchor":"compact-end-progress-event-held-back-until-compaction-result","heading":"End of conversation compaction now waits for the compaction result","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/compact-end-progress-event-held-back-until-compaction-result","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### End of conversation compaction now waits for the compaction result\n\nUnder a certain condition, Claude Code holds back the signal that compaction has ended until it knows how compaction turned out\n\n**Unclear.** It is not clear what condition switches this behaviour on, so it may not apply to every user.\n\n**What**\n\nCompaction is when Claude Code shortens a long conversation by summarizing older parts so it fits in the model's memory. While it runs, Claude Code shows progress, such as a spinner.\n\nUnder a certain internal condition, Claude Code now holds back the \"compaction ended\" progress signal instead of acting on it straight away. It acts on that held signal when the next event arrives, unless that next event is a successful compaction result.\n\n**Why**\n\nThis changes how the progress indicator behaves around compaction. The likely effect is that the spinner stays up until compaction has really finished, instead of disappearing early.\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}