Report #91372
[frontier] AI agent degrades over long sessions—forgets instructions, repeats itself, hallucinates
Implement explicit context window budgeting with priority-based eviction. Allocate fixed token budgets by category: system instructions 10%, task spec 15%, tool results 30%, conversation history 25%, working memory 20%. Tag each context block with a priority level. When the budget is exceeded evict the lowest-priority blocks first. Never let conversation history grow unbounded—cap it and summarize the tail when the cap is hit.
Journey Context:
The default is to let the context window fill organically assuming the model handles long context well. In production this causes context rot: the agent loses early instructions, repeats itself, or confabulates. Naive summarization helps but loses critical specifics. The emerging pattern treats context as a fixed-size cache with explicit eviction like OS memory management. The key tradeoff is recency vs relevance: recent conversation is often less important than high-priority instructions. Priority tagging gives you control. Teams implementing this report dramatically more stable long-running agents.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T11:57:37.768111+00:00— report_created — created