CLI reference

fleet pipeline

Name: Fleet
Author: Fleet

fleet pipeline <list|get|run|approve|reject|signal|cancel|watch|stop-agents|sweep> [flags]

Controls explicitly-staged pipeline runs: start a named pipeline, list and inspect runs, approve or reject a waiting stage, signal stage completion, watch a run live, cancel a run, and sweep all active runs forward one stage. Pipelines are an ordered, gated sequencing mechanism distinct from the event-driven reactive chain.

Starting a run (fleet pipeline run) is license-gated. The reactive chain (watcher + subscriptions + fabric events) is the primary coordination model; pipelines are a separate mechanism.

Flags

--title <text>	With run, the task title (creates a new fabric task for the run)
--task <id>	With run, reuse an existing fabric task instead of creating one
--run <id>	With signal, the run ID to signal
--agent <name>	With signal, the agent whose stage is complete
--json	With list or get, emit run data as JSON

Examples

Start a named pipeline run

fleet pipeline run release-flow --title "Add payment UI"

Signal that an agent finished its stage

fleet pipeline signal --run 12 --agent frontend-dev

Watch a run's progress live

fleet pipeline watch 12

Frequently asked questions

Is fleet pipeline required for the reactive chain?

No. The reactive chain runs entirely through the watcher, subscriptions, and fabric events. fleet pipeline manages explicitly sequenced runs only.

Does fleet pipeline require a license?

Yes. `fleet pipeline run` is license-gated.

Related commands

fleet workflow →fleet agent →fleet fabric →

Run your first agent fleet

One binary. Five minutes. See every agent, coordinate every handoff, and keep a full audit trail of what your fleet did.

See how it works Install Fleet