Agentic RAG: Should the Agent Reason About Where to Retrieve, Not How?
Arc_bong · reddit · 2026-09-04
A Reddit discussion on where agentic RAG actually adds value. The author argues that repeated "search → inspect → search again" loops only make sense for genuine multi-hop questions; with multiple knowledge bases, the agent should reason about where to retrieve (query → route to relevant KBs → parallel retrieval → rerank/merge → answer) rather than micromanaging retrieval itself.
A subtle failure mode: each KB may return good candidates, but the cross-KB fusion layer can still pick wrong context — RRF's rank assumptions break down as sources multiply, and raw similarity thresholds aren't comparable across corpora.
The real design question: what should the agent control, and what stays deterministic? The author compares LangGraph/LangChain, LlamaIndex, and Lyzr's Agent Studio, and asks how production teams draw this boundary.
Related event: Agentic RAG Debate: Route the Query, Don't Just Retrieve(2 posts)→
More from coding & agent
- LukeW's Intent update: multi-agent coordination, workspaces, multi-device runs — LukeW · 2026-09-04
- Intent update coordinates swarms of agents with workspaces across devices — LukeW · 2026-09-04
- VC advice for agentic startups: pitch how your agent recovers from failures — atShruti · 2026-09-04
- WebMCP demo: an AI agent DJs in the browser with hundreds of direct tool calls — No_Guide_8697 · 2026-09-04
- Newsletters, not killer use cases, are what get users to trust agents with real email access — JanJanJaJa · 2026-09-04
- Kafka, Kafka Connect and Schema Registry exposed as native MCP tools — jkriket · 2026-09-04