{"version":"2.1.267","anchor":"confirm-clear-message-cache-markers-option-added-to-compacti","canonical_anchor":"confirm-clear-message-cache-markers-option-added-to-compacti","heading":"Compaction and forked-agent queries can now skip inline cache markers","tier":"use","area":"Compaction","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/confirm-clear-message-cache-markers-option-added-to-compacti","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Compaction and forked-agent queries can now skip inline cache markers\n\nNew skipMessageCacheMarkers option lets compaction and forked-agent requests omit cache markers on messages\n\n**Unclear.** It's unclear what a cache marker on a message does or when skipping it would matter to a user.\n\n**What**\n\n- The internal forked-agent query runner gained a `skipMessageCacheMarkers` option, alongside the existing `skipTranscript`\/`skipCacheWrite` options, threaded into the underlying streaming query call.\n\n- The core compaction\/summarization call now accepts the same `skipMessageCacheMarkers` option (defaulting to false), passed through to the underlying compaction function.\n\n- When enabled, compaction requests omit cache markers on messages under certain conditions, gated by the `tengu_groovy_eclipse` feature flag.\n\n**Why** Cache markers help Claude Code reuse previously-computed context, but they're not always needed; this gives compaction and forked-agent requests a way to skip them when appropriate.\n\n- Area: Compaction\n- Names: `skipMessageCacheMarkers`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 3\/5"}