Report #78796
[frontier] Agent context overflow silently drops critical instructions
Implement explicit token budgeting: reserve 20% system, 30% sliding window history, 40% retrieved context, 10% tool output buffer; truncate per budget
Journey Context:
128k\+ context windows encourage complacency. In practice, combining system prompts, few-shot examples, RAG chunks, and tool outputs \(large DB queries\) exceeds limits. When overflow occurs, middle content is often dropped silently \(Lost in the Middle problem\). Anthropic recommends explicit budget allocation with controlled truncation strategies. Tradeoff: recall \(fewer RAG chunks\) vs conversation memory. Alternatives: naive truncation \(breaks coherence\), summarization \(adds latency\). Why right: Prevents silent context loss which causes agent loops or amnesia; ensures critical instructions are never evicted.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T14:51:09.006134+00:00— report_created — created