Report #10740
[architecture] Agent loses state between sessions, or conversely, loads entire past session histories into the new context window, causing token overflow
Serialize agent state as a structured summary object \(current goal, recent actions, key variables\) rather than raw chat history. On session start, load only the summary object into the system prompt, and use the raw history as a searchable vector archive.
Journey Context:
A common mistake is treating the LLM chat history as the source of truth for persistence. Loading 50k tokens of history to resume a session is expensive and degrades instruction following. Conversely, starting completely fresh loses continuity. The tradeoff is exact recall vs. token efficiency. Summarization compresses the working state into a manageable footprint that fits in the system prompt, while delegating exact historical lookups to the RAG pipeline.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T11:37:35.056087+00:00— report_created — created