Pipelines
List pipelines and manage them as code — pull to JSON, edit, push.
A pipeline is the DAG your agents run — steps, edges (conditions), and triggers. The CLI treats pipelines as portable JSON you can pull, diff, edit, and push back.
The spec
Steps and edges reference each other by step_key, so a pipeline is human-editable
and reusable across orgs. The full JSON schema (conditions, loops, triggers) is in
Pipeline as code.
premia pipelines list
premia pipelines list [--json]ID NAME
p_7f3a Default Pipeline default
p_9b21 Docs-only Fast PathThe default marker shows which pipeline new runs use unless overridden.
premia pipelines pull
Download a pipeline to an editable JSON file.
premia pipelines pull <id> [--out <file>] [--force]| Flag | Description |
|---|---|
--out <file> | Output path. Defaults to ./<id>.pipeline.json. |
--force | Overwrite an existing file. |
✓ Pulled pipeline → p_7f3a.pipeline.json
Edit it, then: premia pipelines push p_7f3a.pipeline.json --id p_7f3apremia pipelines push
Apply a pipeline JSON — update an existing pipeline or create a new one.
premia pipelines push <file> --id <id> # update in place
premia pipelines push <file> --project <slug> # create a new pipelineArguments & flags
| Name | Description |
|---|---|
file (arg) | Path to the pipeline JSON. Required. |
--id <id> | Update this existing pipeline (by public id). |
--project <slug> | Create a new pipeline in this project. Overrides .premia.json. |
✓ Updated pipeline p_7f3aPass either --id (update) or --project (create). With neither — and no
.premia.json in the directory — the command exits 1 and asks you to pick one.
Invalid JSON exits 1; a missing file exits 3.
Recipe — version a pipeline in git
premia pipelines pull p_7f3a --out pipelines/default.json --force
git add pipelines/default.json && git commit -m "snapshot default pipeline"
# …later, after editing…
premia pipelines push pipelines/default.json --id p_7f3a