Report #4244
[architecture] Single-hop vector search failing to retrieve connected concepts
Combine vector search with a knowledge graph \(GraphRAG\) or implement iterative retrieval loops where the LLM generates sub-queries based on initial retrieval results before synthesizing the final answer.
Journey Context:
If a user asks 'What library did the author of the tool I installed yesterday recommend?', a single vector search for the exact query fails. It requires multiple hops: 1\) What tool did I install yesterday? 2\) Who is its author? 3\) What library did they recommend? Pure vector DBs struggle with multi-hop reasoning. The tradeoff is complexity: GraphRAG requires entity extraction and graph maintenance, while iterative retrieval takes more LLM calls and latency. However, without one of these, the agent will hallucinate or fail on complex, relational queries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:05:54.883419+00:00— report_created — created