Qodo Aware

This feature is available for Enterprise users only.

What is Qodo Aware?

Qodo Aware is the code intelligence engine behind the Qodo platform. It connects to all your repos, analyzes architecture and patterns, and powers AI agents that help you search, understand, and solve technical problems.

Think of it as an AI-powered Principal Engineer, that understands your entire system and helps you move faster with confidence.

Why should I use it?

When used inside Qodo Gen, Qodo Aware brings deep, architecture-level understanding directly into your IDE.

You ask the questions, and Qodo Aware finds the answers from across your entire codebase.

How does it work?

Qodo Aware uses Retrieval-Augmented Generation (RAG) and agentic reasoning to understand your codebase:

• Indexing – Builds a deep internal map of your code

• Retrieval – Pulls relevant code, docs, and patterns

• Reasoning – AI agents analyze dependencies and logic

• Generation – Produces grounded, accurate responses

---

What can Qodo Aware do?

Qodo Aware uses two types of AI agents to answer your questions. You can switch between the agents, depending on the complexity of the task.

You can switch agents by clicking the Qodo Aware button above the chatbox.

Ask Agent

• Best for quick, targeted codebase Q&A.

• Use it to understand functions, trace logic, or ask how a specific component works.

Example: "Where is this middleware used in the login flow?"

Deep Research Agent

• Ideal for complex planning, refactoring, and architecture questions.

• Performs multi-step reasoning across services and layers of your system.

Example: "What are all the components affected if we refactor how session tokens are handled?"

---

Using Qodo Aware

Tag Your Codebase

To enable Qodo Aware, you first need to tag the repositories you want it to understand. This gives the AI the context it needs to generate accurate, grounded responses.

You can tag one repository or your entire codebase.

1. Tag your repositories

Option 1: Quick Tag via Chat

• Type @ in the chatbox.

• From the menu, select Company's Codebase.

Option 2: Use the @ Button

• Click the @ button above the chatbox.

• From the menu, select Company's Codebase.

Search and select the repositories you want to include in Qodo Aware.

You can tag individual repos or use tags (e.g., "frontend", "payments", "core-services"). Tags can be configured in the configuration file.

Once tagged, Qodo Aware is automatically activated for those repositories, meaning it acquires deep understanding about them and is able to answer complex questions.

---

What Happens After Tagging?

Once you've tagged your repositories:

• Qodo Aware indexes and maps the selected codebases.

• It understands how components relate across files, services, and versions.

• It uses that deep understanding to answer your questions and suggest change, just like an experienced engineer who knows your code inside and out.

---

Tips for Getting the Most Out of Qodo Aware

• Be specific in your prompts when working on complex systems. It’ll trace the logic or dependencies for you.

• Use tags to keep responses scoped to relevant services or projects.

• Try Deep Research Agent when planning a refactor, migration, or major feature change.

---

Example Usage

New hires New domain New projects Working with unfamiliar coding language	Quickly learn code behaviors Get overview of functions or files Map coding patterns across the codebase	"How does acme handle API errors and retries?"
Cross-Repo Feature Planning	Plan features spanning multiple repositories by understanding dependencies and integration points.	"Plan rate limiting for login flow across all our repos"
Reducing Duplicated Code	Search within organization codebase for semantic similarities to reduce code duplication	“Where do we already use a function like this?”
Coding patterns	Suggest code that follows patterns and standards	"Show me an example of how pagination is implemented in the user-service."
Detecting dependencies and breaking changes	Search within organization codebase for components that may break from the changes	“Review diff with remote codebase and identify components that are affected or may break”