Logic measuring how long you've been idle logs what a cache stop would do without doing it.
Idle cache-stop policy runs in shadow mode behind an off-by-default internal flag.
What's wrong with this entry?
New logic tracks main-loop request timing, when you last typed, and any delegated or background work in order to compute how long a session has been idle, then logs what a cache stop would have done. It does not act on that decision in this build, and the whole thing is behind an internal flag that defaults off.
- Purely observational: the computed stop is recorded, never applied.
tengu_cache_heartbeat_shadow
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.248
Turns with different suppression settings are no longer confused for each other
Both mention caching
-
v2.1.248
Prompt-cache-break explanation split into its own function
Both mention caching
-
v2.1.248
Cache diagnostics keep the previous request body directly
Both mention caching