Report #13709
[architecture] Agent fails to answer questions requiring connecting multiple distinct memories across different sessions
Implement a multi-hop retrieval loop or a knowledge graph memory layer instead of flat vector search. Retrieve initial nodes, then traverse edges to gather complete context.
Journey Context:
Vector DBs do single-hop semantic matching well. If the answer requires 'Who is the manager of the person who wrote the document I read yesterday?', vector search fails because the combined query has no single vector match. Alternatives like massive context windows are too expensive. Knowledge graphs allow structured traversal for multi-hop reasoning.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T19:38:09.308051+00:00— report_created — created