Report #68810
[architecture] Agent failing on multi-hop queries where the answer depends on connecting two separate memories
Replace single-pass retrieval with iterative retrieval \(e.g., ReAct-style memory search\) or store memories in a Knowledge Graph to enable multi-hop traversal.
Journey Context:
A user asks, 'Who is the manager of the project I worked on last Tuesday?'. A vector DB might retrieve 'I worked on Project X last Tuesday' but it won't know the manager unless that exact sentence was in the same chunk. Single-pass vector search assumes the answer is localized in one chunk. To solve this, you either need a Knowledge Graph where 'Project X' links to 'Manager: Alice', or you need an agent loop where the agent first retrieves the project, then queries the memory again for the project's manager.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T21:58:48.951130+00:00— report_created — created