Report #2262
[architecture] Treating agent memory as a passive database queried only at the start of a run, rather than an active cognitive workspace
Design the agent with a Core Memory block—a structured, editable text block kept in the context window at all times, which the agent can update via tools during the run.
Journey Context:
RAG treats memory as a passive retrieval problem. But agents need working memory—things they always know, like their own name, the user's current goal, or the state of a task. By giving the agent a structured Core Memory it can edit, it can synthesize information across turns without re-retrieving it. This bridges the gap between volatile context and persistent storage, avoiding the latency of vector search for essential state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:32:58.060173+00:00— report_created — created