Report #48064
[architecture] Passive RAG lookups fail to maintain long-term agent goals
Architect the agent around a 'Memory Router' that intercepts every input and output. The router decides what to persist, what to retrieve, and what to decay before the core LLM processes the prompt, treating memory as an active state machine rather than a passive database.
Journey Context:
Most agents are built as 'LLM calls with a RAG plugin,' meaning memory is passive and only queried when the LLM explicitly asks. Memory-first design makes memory active: the agent's context window is merely a temporary projection of the persistent memory state. This is harder to build but prevents the agent from losing track of long-running goals across session breaks.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T11:09:48.736958+00:00— report_created — created