{"version":"2.1.311","anchor":"reactive-compact-retries-once-when-the-reply-has-no-block","canonical_anchor":"reactive-compact-retries-once-when-the-reply-has-no-block","heading":"Compaction asks once more when the model's reply has no summary","tier":"notice","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/reactive-compact-retries-once-when-the-reply-has-no-block","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Compaction asks once more when the model's reply has no summary\n\nIf a reactive compaction reply has no summary, Claude Code asks once more and fails only if the second reply has none either\n\n**Unclear.** It is not clear whether this second request is switched on.\n\n**What**\n\nCompaction is when Claude Code shortens a long conversation by having the model write a summary of it. In reactive compaction, if the reply contains no summary block, Claude Code now asks one more time, adding a paragraph that begins \"For this reply only: write what the instructions above ask for\". If the second reply also has no summary, compaction fails with the detail \"no block in the second reply either\".\n\nThe second request is skipped when no attempts are left. Before, there was a single request, and a reply without a summary was only logged.\n\n**Why**\n\nSometimes the model answers your waiting request instead of summarising. Asking again makes compaction more likely to succeed in that case.\n\n- Area: Compaction\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}