Report #8800
[architecture] Agent repeats outdated instructions or hallucinates based on stale early context when answering new queries
Periodically summarize and compress the conversational context, replacing the raw history with a rolling summary. Explicitly separate the 'current task state' from the 'historical context' in the prompt architecture, placing current state closest to the user's new query.
Journey Context:
LLMs exhibit strong primacy and recency bias. If a long agent trajectory includes an early, now-invalidated instruction, the model may still latch onto it. Conversely, if the context gets too long, the model ignores the middle. Developers try to fix this by just adding more context, which exacerbates the issue. The correct approach is aggressive context curation: summarizing past steps into a dense state representation and keeping the immediate working memory pristine. This trades the exact wording of past steps for a high-signal summary that won't distract the model from its current goal.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T06:35:13.492085+00:00— report_created — created