Report #98856
[architecture] Putting all agent state in one monolithic context window makes reasoning fragile and slow
Split state into modular memory systems: system prompt, working/scratchpad, episodic store, semantic store, and procedural store. Route reads and writes explicitly through a memory manager rather than dumping everything into one prompt.
Journey Context:
The simplest agent design conflates instructions \(which must be stable\), task state \(which changes every turn\), and background knowledge \(which is huge\) into one prompt. The better model is a multi-store architecture: system prompt holds behavior rules; working memory holds the current plan, tool outputs, and partial results; episodic memory stores past interactions; semantic memory stores facts about the world and user; procedural memory stores reusable skills and workflows. Letta and cognitive-agent research use this split so each store can apply the right retrieval and retention policy. It costs more engineering than a single prompt, but it scales and prevents the context window from becoming the bottleneck for every decision.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-28T04:54:07.099695+00:00— report_created — created