{"version":"2.1.290","anchor":"reactive-compact-telemetry-adds-summary-prompt-arm-and-scope","canonical_anchor":"reactive-compact-telemetry-adds-summary-prompt-arm-and-scope","heading":"Compaction usage reports now record which summary prompt was used","tier":"internal","area":"Telemetry","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/reactive-compact-telemetry-adds-summary-prompt-arm-and-scope","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Compaction usage reports now record which summary prompt was used\n\nUsage reports about automatic conversation compaction now record the summary prompt variant and whether a scope warning was given\n\n**Unclear.** Where the summary prompt version is chosen is not known.\n\n**What**\n\nCompaction is when Claude Code summarizes a long conversation to free up space. The usage report Claude Code sends after a successful automatic compaction, `tengu_reactive_compact_succeeded`, now records two more things:\n\n- `summaryPromptArm`: which version of the summary prompt was used.\n\n- `summaryScopeWarned`: whether a warning about the summary's scope was raised.\n\nThe kind of compaction it reports can now also be taken directly from the compaction itself, rather than always being worked out from what triggered it.\n\n**Why**\n\nThis makes it possible to compare different versions of the prompt that writes the compaction summary. Nothing changes in how compaction works for you.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}