Report #11115
[architecture] Agent relies solely on vector similarity search for memory, failing to retrieve sequential, multi-step reasoning or exact past actions
Separate memory into Semantic \(facts/embeddings\) and Episodic \(chronological logs/trace\). Use vector search for semantic, but sequential or graph search for episodic memory.
Journey Context:
Vector DBs are great for 'find me the document about X' but terrible for 'what did I do step-by-step to fix Y yesterday?'. Embedding a whole trajectory loses the order. Episodic memory preserves the sequence of actions. The tradeoff is that episodic memory grows fast and is harder to search without time bounds, so it requires strict retention policies.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T12:37:15.341879+00:00— report_created — created