C6 · Agentic search

Family: Single agent

The agent decides what to look for, reads, judges relevance and tries again, instead of receiving pre-selected passages.

Principle

In a loop, the agent writes its queries, reads the results, judges whether they are enough and refines its search. It keeps light identifiers (paths, queries, links) and loads data on demand rather than preprocessing everything. This is agent-driven RAG.

The problem it solves

A fixed RAG chain returns a batch of passages chosen before the question is understood, and cannot recover from a missed first search.

When to use it

  • You search structured text, such as code, where simple tools (grep, ls) work well.
  • You cannot tell in advance how many reads will be needed to answer.

When to avoid it

  • The corpus is large and unstructured: vector RAG remains the foundation, and the agent complements it rather than replacing it.
  • The answer must fit in one quick pass: an augmented LLM with retrieval (A1) avoids search cycles.

Common pitfalls

The anti-patterns that misuse this pattern, best established first. Each sheet describes the symptoms, the public incidents and the remedies.

Tools and agent-computer interface

Security and permissions

Oversight, operations and governance

All anti-patterns

Synonyms by vendor

  • Agentic RAG (Singh et al. (2025))
  • Recherche « juste à temps » (just-in-time retrieval) (Anthropic (context engineering))

Neighbouring patterns

Sources

Content reviewed on 2026-10-02

Pattern catalogue