Skip to main content
Potpie reads existing patterns, conventions, and dependencies from the knowledge graph before writing a line of code. It maps the request against what already exists, generates a specification and architecture plan, and presents every change as a reviewable diff. Code reaches the repository only after diff approval.

Workflow

1

Describe the feature

Enter a description of the feature to build. Potpie asks clarifying questions before generating anything.Feature description input
2

Clarifying questions

Potpie surfaces a set of clarifying questions as multiple choice options. Answers lock in the scope and requirements before the specification begins.Clarifying questions
3

Specification

Potpie parses the codebase against the confirmed requirements and generates a specification covering every file to create or modify, implementation details for each change, and dependency relationships between affected components.Specification page
4

Plan

Once the spec is confirmed, Potpie generates a plan.
An explanation of what changes, which parts of the codebase are in scope, and how the new code fits the existing system.Plan summary tab
5

Code generation

Potpie generates the code and presents every change as a diff. Changes match the existing code style and conventions identified during specification.Code generation diff view
6

Pull request

Clicking Create PR pushes the full diff to the repository.Final review before PR

Multi-agent mode

Potpie runs in two modes depending on request complexity:
  • Single agent: Potpie handles the full request from start to finish.
  • Multi agent: Potpie’s subagents can do research as well as coding.
Potpie determines the mode automatically.

Using the API

The Create Conversation and Message endpoint opens a session against a parsed project and returns the specification and plan in a single call.

Example uses