What gets parsed
Every source file breaks down into typed nodes.| Node type | What it captures |
|---|---|
Function / Method | Signature, parameters, return type, call sites, and the file it lives in |
Class | Fields, methods, inheritance chain, and every file that instantiates or extends it |
Module / File | Exports, imports, and the dependency relationships between files |
Potpie indexes each branch independently, so queries always reflect the exact state of code on the selected branch.
How relationships are mapped
Relationships between nodes become typed edges in the graph.| Edge type | What it represents |
|---|---|
Calls | A function invoking another function |
Imports | A file or module depending on another |
Extends | A class inheriting from another |
Implements | A class implementing an interface or contract |
Every edge carries directionality. The graph records which component depends on which, giving agents a precise map of every dependency in the codebase.
How agents use it
Ask
Traces a flow by traversing edges from the entry point outward.
Build
Reads dependency edges around every file it plans to modify before generating a spec.
Debug
Follows the call chain backwards from the point of failure to identify a root cause.