Workflows
A Fleet workflow is an explicit, saved graph of work. You build it in the dashboard; your self-hosted worker executes it and records what happened.
The execution model
Build and save in the dashboard
↓
Trigger a run: manual, label, schedule, or KPI
↓
Self-hosted worker claims the run
↓
Execute the typed workflow graph
↓
Pause for PRs or human approval when required
↓
Record artifacts, decisions, retries, and terminal statusLabels are one way to trigger an explicit workflow. They do not wake agents by matching event subscriptions. The workflow definition owns every dependency, route, retry, and sign-off boundary.
Four things to know
Definition
The saved graph: repo, trigger, typed steps, dependency edges, outcome routes, and governance.
Run
One execution of a definition, with its own state, inputs, artifacts, decisions, retries, and provenance.
Worker
Your self-hosted Fleet process. It pulls pending runs and executes agent steps in the selected repo.
Artifact
A content-addressed, versioned output with lineage back to its workflow, step, inputs, rules, and model.
Build one
- 1Open Workflows in the Fleet dashboard and choose New workflow.
- 2Choose a template or start blank. Templates are ordinary editable definitions.
- 3Select the repository. It is the code working tree, ticket system, and run scope.
- 4Add typed steps and drag connections to define dependencies.
- 5Configure outcome routes, retry limits, and approval recipients.
- 6Choose a manual, label, schedule, or KPI trigger.
- 7Save, run, and open History to inspect the result.
Starter templates
| Template | Shape |
|---|---|
| Weekly brief | Gather notes → write a risk-first brief |
| Summarize → report | Summarize documents → synthesize a report |
| Release notes | Turn raw change notes into customer-facing copy |
| Ship a feature | Refine → code → review/fix → approve → merge → announce |