Overview

With Potpie, developers can interact with their codebase in three distinct ways, via-asking questions, generating code, and debugging issues. Every interaction mode operates on the same underlying knowledge graph, ensuring that every response is grounded in a consistent, structured understanding of the system.

​

How It Works

Every interaction in Potpie, flows through a unified interface. For every query, it includes the full conversation history, the active project context, and any specific files or nodes referred by the user. Prior to any reasoning, the agent retrieves the actual source code associated with those references and loads it into context, thereby ensuring that all responses are grounded in real code rather than abstract summaries or descriptions. Based upon the complexity of the task, Potpie either operates as a single agent or delegates execution to specialized subagents. This orchestration is determined by the nature and scope of the request itself, not by any manual user configuration.

​

Three Modes

Ask : for understanding the codebase. It answers questions about how something works, where something lives, what something does, and why something was built the way it was. Build : for making changes. It reads existing patterns and conventions from the knowledge graph prior to writing a single line, and then generates code that matches the style and structure of the codebase. Debug : for tracing issues. It follows a problem from where it surfaces back to where it originates, identifies the root cause in the graph, and returns a targeted fix.