{"version":"2.1.281","anchor":"reactive-compact-passes-a-reactive-flag-into-post-compact","canonical_anchor":"reactive-compact-passes-a-reactive-flag-into-post-compact","heading":"Reactive compact passes a 'reactive' flag into post-compact attachment rebuild","tier":"internal","area":"Compaction","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/reactive-compact-passes-a-reactive-flag-into-post-compact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Reactive compact passes a 'reactive' flag into post-compact attachment rebuild\n\nAfter a successful emergency compaction, rebuilding attachments now knows it was reactive\n\n**Unclear.** The finding does not say what the rebuild does differently for reactive compactions or what the extra step does.\n\n**What**\n\nCompaction shortens a long conversation by summarizing older parts. Reactive compaction is the version that runs after the model has rejected a conversation as too long. When it succeeds, Claude Code rebuilds the attached context, such as files, and that step is now told whether the compaction was reactive. It also runs one extra step on the content being kept.\n\n**Why**\n\nRebuilding after compaction can now behave differently when the compaction was an emergency one.\n\n- Area: Compaction\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}