✨ Visual Editor

close

palette Canvas & Background

Gradient:arrow_forward
Text Color:
135°

style Card Style

40px
16px

text_fields Typography

16px
Avi Chawla
@_avichawla
Naive RAG vs. Agentic RAG, clearly explained (with visuals):
Avi Chawla
@_avichawla
Naive RAG has many issues:

- It retrieves once and generates once. If the context isn't enough, it cannot dynamically search for more info.

- It cannot reason through complex queries.

- The system can't modify its strategy based on the problem.
Avi Chawla
@_avichawla
Agentic RAG attempts to solve this.

The following visual depicts how it differs from naive RAG.

The core idea is to introduce agentic behaviors at each stage of RAG.
Avi Chawla
@_avichawla
Steps 1-2) An agent rewrites the query (removing spelling mistakes, etc.)

Step 3-8) An agent decides if it needs more context.

↳ If not, the rewritten query is sent to the LLM.
↳ If yes, an agent finds the best external source to fetch context, to pass it to the LLM.
Avi Chawla
@_avichawla
Step 9) We get a response.

Step 10-12) An agent checks if the answer is relevant.

↳ If yes, return the response.
↳ If not, go back to Step 1.

This continues for a few iterations until we get a response or the system admits it cannot answer the query.
Avi Chawla
@_avichawla
This makes RAG more robust since agents ensure individual outcomes are aligned with the goal.

That said, the diagram shows one of the many blueprints an agentic RAG system may possess.

You can adapt it according to your specific use case.
Avi Chawla
@_avichawla
If you found it insightful, reshare it with your network.

Find me → @_avichawla
Every day, I share tutorials and insights on DS, ML, LLMs, and RAGs.
Generated by Thread Navigator
100%
view_carousel Carousel Studio NEW
Press + S to quick-export