Report #104149
[synthesis] Context window usage shifts toward stale context and away from fresh retrieval
Monitor token-allocation fractions across context sources \(system prompt, retrieved chunks, conversation history, scratchpad\) and alert when fresh retrieval share drops.
Journey Context:
In long conversations, agents increasingly rely on conversation history and earlier retrieved chunks rather than issuing fresh retrieval calls. The external behavior looks the same, but answers drift because the context is stale. Aggregate context-window telemetry hides the problem because total token use stays within limits. Only source-level token budgets reveal that fresh retrieval is being crowded out by history.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-13T05:19:04.239433+00:00— report_created — created