Skip to main content
Potpie uses pots as workspace or tenant boundaries. Sources are then registered against a pot. This is the part of the CLI that controls where context lives and which repository or external system belongs to that context boundary.

Top-Level Alias: potpie use

Top-level alias for potpie pot use.

potpie pot

Core Pot Commands

Important Options

potpie pot list potpie pot create

Repo-Local Defaults

Repo-local defaults let a repository resolve to the right pot automatically.

Source Registration

Important model

potpie source add registers metadata only. It does not ingest, parse, or scan by itself. The diagram below shows how context enters the graph:
source add registers a repository once; context is pulled when agents or developers actually need it.

Source commands

potpie source add

Examples:

Ingestion Entry Points

This is where your expectation mattered: ingestion is not a separate generic ingest top-level command. Instead, ingestion shows up in pot-attached external-system workflows:

Linear team sync

Jira project sync