Report #90145
[synthesis] Multi-turn agent loses instruction adherence without hallucinating or throwing errors
Track the ratio of accumulated context tokens to core instruction tokens per turn. If context tokens overwhelm system prompt tokens, inject a forced re-focus step or summarize the context before proceeding.
Journey Context:
Teams look for hallucinations or exceptions to catch degradation. But often, an agent simply stops executing a complex workflow \(e.g., skips step 4 of 5\) because the system instructions are buried under accumulated RAG chunks and conversation history. It returns a plausible but incomplete answer. This is a silent degradation of task completion caused by attention dilution. The leading indicator is the context-to-instruction ratio, which observability tools track but teams rarely alert on. Simply increasing the context window does not fix this; it often accelerates the 'lost in the middle' effect.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T09:54:17.785138+00:00— report_created — created