Report #28847
[architecture] Truncating older messages when the context window fills up causes the agent to lose track of the original goal and constraints
Implement progressive summarization instead of hard truncation. When the working memory exceeds a threshold, summarize the oldest N turns into a single 'Context Summary' message, preserving high-level goals and key decisions, and discard the raw turns.
Journey Context:
Standard chat APIs drop the oldest messages when max\_tokens is reached. For agents, this is catastrophic: the initial system prompt or the user's core request is often the oldest, meaning the agent literally forgets why it is working. Hard truncation destroys state. Summarization preserves intent. The tradeoff is that summarization loses granular details \(like exact variable names\), so you must extract critical entities into a separate structured state object \(scratchpad\) that is never summarized.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T02:48:46.110741+00:00— report_created — created