How It Works
Understand the Question
The agent classifies every incoming question into one of four types:- What covers functionality and purpose
- How covers implementation and flow
- Where covers location and usage sites
- Why covers rationale and design decisions
For complex or multi-part questions, the agent tracks what needs answering and breaks exploration into individual tasks before any navigation begins.
Navigate the Codebase
The agent moves from broad to narrow, starting by finding where relevant functionality lives in the knowledge graph. It then understands directory layout and module organization, retrieves specific named classes or functions, and batch-fetches all relevant nodes collected so far. From there it maps what calls the code and what the code calls, retrieving full files or specific line ranges as needed, and reading multiple files simultaneously when broad context is required. It also searches file contents directly by pattern to locate usage sites and definitions not reachable through the graph alone. If the question involves a third-party library, the agent retrieves external documentation to supplement its answer when required.Respond
Answers are structured using clear section headings such as Main Answer, Details, Code Examples, and Related Components. They are grounded in the codebase with file path and line number citations where relevant, and all code snippets are presented in fenced blocks with appropriate language tags for clarity. Before returning, the agent verifies that all aspects of the question are answered and all exploration tasks are complete.Calling the Agent
conversation_id, send your question:
Next Steps
- See Debugging Agent to trace and fix issues across the codebase
- See Code Generation Agent to generate and modify code

