Skip to main content
The Debug Agent traces a reported issue from where it surfaces to where it originates. It walks the knowledge graph across every affected component, pins the root cause to an exact file and line, and returns a targeted fix.

​
Getting started

1

Describe the issue

Paste an error message, stack trace, or describe the unexpected behavior. Include any context about when it occurs.Describing the issue
Follow up messages within the same session retain full context. Start with a high-level symptom and narrow to the root cause across subsequent turns.
2

Potpie investigates

The Debug Agent applies its eight step methodology automatically: validating the behavior, traversing code paths, pinning the root cause, and generating a targeted fix.Debug agent investigating

​
Eight-step methodology

Potpie applies an eight step methodology to every issue:
1

Understand and validate

Confirms the reported behavior against the codebase, identifies every component involved, and establishes what the correct behavior should be at the point of failure.
2

Explore and hypothesize

Traverses the relevant code paths in the knowledge graph and generates candidate explanations for the failure.
3

Identify the root cause

Pins the failure to a specific file and line, identifying the exact instruction that introduces the faulty state.
4

Generalize the issue

Checks whether the same defect pattern appears elsewhere in the codebase.
5

Design a solution

Generates a targeted fix scoped to the root cause.
6

Scrutinize and refine

Evaluates the fix against edge cases and traces potential side effects through the dependency graph.
7

Implement

Produces the corrected code with exact file paths and line references.
8

Final verification

Validates the fix against the original failure and checks for regressions.

​
Investigation mode

Potpie resolves straightforward issues end to end. For failures that span multiple services or require deep dependency traversal, Potpie delegates to specialized subagents.

​
Using the API

The Create Conversation and Message endpoint opens a debug session against a parsed project and returns the first investigation response in a single call.

​
Example uses

Null Pointer

Tracing a null pointer exception to its origin across service and data layers.

Memory Leak

Tracing a memory leak in a long-running service to its source across object lifecycle and dependency chains.