Report #91998
[architecture] Agent fails to answer questions requiring connecting multiple disparate pieces of information because single-pass vector search only returns locally similar chunks
Implement multi-hop retrieval: prompt the agent to generate sub-queries, retrieve documents for each, and then use a reasoning step to synthesize the answer across the retrieved sets, or use a graph database where edges explicitly connect the entities.
Journey Context:
Vector similarity is a lexical/semantic proximity heuristic. If the answer requires 'Who is the CEO of the company that acquired the startup founded by John?', a single vector search will likely fail because the text probably does not contain all those words in one paragraph. Graph RAG is an alternative but requires heavy upfront entity extraction. Multi-hop retrieval bridges the gap by allowing the agent to follow a chain of citations across the vector space iteratively.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T13:00:39.511504+00:00— report_created — created