Agentic Retrieval: The Loop That Decides When to Search

Originally published at Agentic Retrieval: The Loop That Decides When to Search on smartgate.network.

A shorter version of "Agentic Retrieval: The Loop That Decides When to Search" — the full piece lives at smartgate.network.

What the full piece covers

• agentic retrieval: the loop, and what it changes about retrieval — A retrieval-augmented pipeline retrieves once.
• agentic search: one tool call, and the loop hiding inside it — An agent sees a search tool as a function: a string in, a list of results out.
• The loop in four moves — It is worth writing the loop down as four decisions rather than as a prompt, because each move takes a different input, produces a different artefact, and fails differently.
• Stopping conditions: what can actually end the loop — An agent's judgement that it has enough is a useful signal and useless as a guard: the step that wants another search is the step that would have to enforce the limit.
• Two failure modes: over-retrieval and under-retrieval — Loops do not fail symmetrically: the two directions need different numbers to detect and different fixes to correct, so naming which one you have is most of the diagnosis.
• context compression: the alternative the loop should price first — When the window is the binding constraint, the loop has two options that look different and compete for the same budget: fetch less, or shrink what it already holds.
• llm memory: the loop's second retrieval path — The decide move does not have to resolve to a search.
• memory agent: what the loop is allowed to write back — Every loop that stops also decides, somewhere, what to keep.
• firecrawl alternative: the tool choice is a loop decision — Because the model cannot see inside the tool, the tool's failure modes become the loop's.
• url to markdown: what the loop gets back into the window — Search returns pointers; the loop usually needs text.
• agent memory systems: the ledger that turns retries into a loop — An agentic loop needs somewhere to record what it has already asked and learned.
• Where SmartGate fits: the loop's enforcement boundary — Every call a loop makes can cross one place in our own stack, where two of the four moves stop being prompt-level intentions.
• …plus 1 more section(s).

Read the full piece: Agentic Retrieval: The Loop That Decides When to Search on smartgate.network.