New skipMessageCacheMarkers option lets compaction and forked-agent requests omit cache markers on messages
What
- The internal forked-agent query runner gained a
skipMessageCacheMarkersoption, alongside the existingskipTranscript/skipCacheWriteoptions, threaded into the underlying streaming query call. - The core compaction/summarization call now accepts the same
skipMessageCacheMarkersoption (defaulting to false), passed through to the underlying compaction function. - When enabled, compaction requests omit cache markers on messages under certain conditions, gated by the
tengu_groovy_eclipsefeature flag.
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.
tengu_groovy_eclipse Off by default, switched on for this accountThe shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.
This account: on · anonymous baseline: on · compiled default in v2.1.267: off
Read once, for one account on one subscription tier, against v2.1.267. It isn't a statement about your account. What a flag value here can and cannot tell you
New in this build: tengu_groovy_eclipse