Short-lived messages no longer invalidate the prompt cache, so more context gets reused.
What's wrong with this entry?
Cache markers, which decide how much of a conversation the model can reuse between requests, now step over ephemeral user messages when placing themselves, so short-lived messages do not invalidate the cache.
- Ephemeral user messages are treated like system entries during the backwards walk.
- The trailing-system optimisation is refused if an ephemeral user message sits in between.
- Fork-point pinning is skipped entirely when a top-level cache control is supplied.
(fe.type === "user" && fe.ephemeral === !0)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Post-compaction file restore skips memory files
Both mention compaction
-
v2.1.219
Tool-result eviction no longer double-counts already-seen results
Both mention compaction
-
v2.1.219
Compaction hook plumbing reworked
Both mention compaction