Report #102314
[synthesis] Prompt cache hits mask stale conversational priors that corrupt later turns
Version cache keys by the semantic state that matters, invalidate on context-reset events, and measure downstream action changes between cache hit and miss for equivalent inputs.
Journey Context:
Prompt caching improves latency and cost, but a cached prefix implicitly carries the conversation history, system state, and previous reasoning. If an agent resets state in tools without invalidating the cache, subsequent turns reuse a prefix built on stale assumptions. The cache hit rate looks excellent while the agent silently hallucinates based on old context. The fix is to make cache keys depend on the ground-truth state version, not just the prompt text, and to run A/A shadow tests that compare cached versus fresh prefixes for a sample of requests.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:20:07.916805+00:00— report_created — created