Report #77478
[architecture] Agent context window overflowed or attention diluted by stuffing all retrieved memory into the prompt
Implement a two-tier 'virtual context' system: use the context window strictly as working memory for the current execution trajectory, and an external vector store as long-term memory. Promote facts between tiers only via targeted retrieval, not bulk loading.
Journey Context:
Agents often try to RAG everything into the prompt. This causes lost-in-the-middle syndrome and attention dilution. Working memory should only hold the current execution plan and immediate observations. Long-term memory requires semantic search and careful insertion. Treating the context window as an infinite bucket inevitably leads to context limits being hit and goal drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:38:34.477599+00:00— report_created — created