Configuration
Local configuration describes where workflows execute and which agents can do the work. Workflow graphs themselves are authored and saved in the dashboard.
Project config
.fleet/config.yaml belongs to one repository:
repo: acme/payments
default_branch: master
source_control: github
types:
- name: backend-developer
vendor: claude-code
model: claude-sonnet-4-6
prompt: |
You implement small, testable backend changes.
- name: tech-lead
vendor: claude-code
model: claude-opus-4-7
agents:
- name: backend-dev-1
role: backend-developer
isolation: worktree
max_concurrent: 2
- name: reviewer-1
role: tech-lead
isolation: worktree
use_github_app: true
corpus:
- path: docs/**/*.mdThere is no subscribes_to, subscribe_mode, orsubscription_gate field. Those belonged to the retired subscription execution model. Configure triggers and outcome routes on the saved workflow instead.
Repository fields
| repo | Full owner/repo name. Used for workflow scope, tickets, and code working trees. |
| default_branch | Default PR base and merge target. Falls back to master when empty. |
| integration_branch | Optional additional release-train target. |
| source_control | github by default; gitlab is supported by the provider abstraction. |
| source_control_base_url | API base for a self-managed source-control installation. |
| ci_required | Observable repo policy. It does not independently enable a merge check. |
Agent types
A workflow step binds an agent type through its role. Types provide shared prompt, vendor, and model defaults. A named agent can override vendor or model, but it still belongs to the type named by its role.
House rules are managed separately in the control plane and matched by role. The worker pins the applicable rule versions when a run starts, so a mid-run edit cannot silently change resumed work.
Agent fields
| Field | Type | Purpose |
|---|---|---|
| name | string | Unique agent instance name within the project. |
| role | string | Agent type used by workflow steps and house-rule matching. |
| vendor | string | Runner vendor override; public workflows use Claude Code. |
| model | string | Per-agent model override. The type default applies when empty. |
| enabled | bool | Whether Fleet may select and start this agent. |
| isolation | string | Set to worktree for a dedicated git worktree per run. |
| max_concurrent | integer | Maximum parallel sessions for this agent; default 1, -1 is unlimited. |
| department / team / reports_to | string | Organization metadata used by roster and reporting surfaces. |
| use_github_app | bool | Use a short-lived installation token for a distinct GitHub identity. |
Org config
Org configurations live under ~/.fleet/orgs/<name>/org.yamland group multiple repositories under one watcher host.
name: acme
workspace: ~/src/acme
repos:
- acme/payments
- acme/web
types:
- name: tech-lead
vendor: claude-code
model: claude-opus-4-7The org watcher starts one workflow worker for each managed repo. It does not run an org-wide subscription processor.
Corpus and connectors
Corpus entries select repository files for document steps. Use fleet corpus resolve to inspect matches. Connector instances materialize external data snapshots that workflow steps can consume; their health and freshness appear alongside other integrations.
Dashboard definitions versus local genflows
Customer workflows are authored in the dashboard and pulled by the worker. The binary can also parse a local genflows: block for local execution, linting, and integration tests. Treat that as an advanced CLI surface, not the primary authoring path. The older workflows:block and fleet workflow command refer to a separate legacy trigger/action rule subsystem.
Validate changes
fleet doctor
fleet status
fleet genflow lint --dir .
fleet corpus resolve