{"version":"2.1.283","anchor":"reactive-compaction-now-drives-the-streamingresponse-length","canonical_anchor":"reactive-compaction-now-drives-the-streamingresponse-length","heading":"Automatic compaction reports summary progress the way a normal reply does","tier":"internal","area":"Compaction","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/reactive-compaction-now-drives-the-streamingresponse-length","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Automatic compaction reports summary progress the way a normal reply does\n\nAutomatic compaction now reports how much of its summary has streamed in, using the same progress events as a normal reply\n\n**Unclear.** It is not clear whether or how this progress is shown on screen.\n\n**What**\n\nCompaction is when Claude Code summarises a long conversation to free up room. When it starts compaction automatically, it now sends the same progress events that a normal reply sends: a \"requesting\" status and a running count of how long the response is so far. Before, it sent only its own compaction progress and status events.\n\n**Why**\n\nThe length of the summary can now be followed as it streams in, the same way as for an ordinary reply.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}