{"version":"2.1.300","anchor":"compaction-after-compaction-output-cap-simplified","canonical_anchor":"compaction-after-compaction-output-cap-simplified","heading":"Reply length cap after compaction is checked a different way","tier":"internal","area":"Compaction","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/compaction-after-compaction-output-cap-simplified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Reply length cap after compaction is checked a different way\n\nThe check deciding when to cap reply length right after compaction now uses a shared helper instead of its own inline test\n\n**What**\n\nCompaction is when Claude Code shrinks a long conversation into a summary so it fits. There is a setting mode that caps how long the model's reply can be just after compaction. The check for whether that cap applies used to look directly for a user message after the compaction. It now hands that check to a shared helper.\n\n**Why**\n\nThis reorganises an existing check rather than adding anything new.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}