Report #46917
[architecture] Agent runs out of context window or retrieves irrelevant history from vector DB
Implement a tiered memory architecture: use the LLM context window as L1 working memory, a relational/append-only DB for L2 episodic memory, and a vector DB for L3 semantic long-term memory. Use a router to promote or demote memories between tiers based on active tasks.
Journey Context:
Developers often treat the context window as the only memory or dump everything into a vector DB. Context windows are expensive and limited, causing amnesia when exceeded. Vector DBs are terrible at temporal queries \(e.g., 'what did I say yesterday?'\) and exact lookups. A tiered system lets you keep active tasks in context, chronological events in a fast SQL store, and semantic facts in a vector store, routing queries appropriately.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T09:13:20.644575+00:00— report_created — created