Team templates¶

A template is the blueprint a team is created from: which roles exist, which agent each role runs, the model alias and VM profile of each, how many replicas and concurrent runs, when to sleep, the daily budget and the pipeline between roles. Editing a template adds a version and makes it current; teams created earlier keep their own settings until refreshed.

lead: planner
roles:
  planner:  { agent: planner,  model: frontier,    vm: small,  replicas: { max: 1 }, concurrent_runs: 3 }
  coder:    { agent: coder,    model: local-coder, vm: medium, replicas: { max: 3 }, concurrent_runs: 1 }
  reviewer: { agent: reviewer, model: frontier,    vm: small,  replicas: { max: 1 }, concurrent_runs: 2 }
sleep: { idle_after: 10m, deep_sleep_after: 24h }
budget_usd_per_day: 50
isolation: shared
rework_rounds: 2
pipeline: { coder: reviewer, reviewer: planner }

Field	Meaning
`lead`	The role every work item starts with and the only one that talks to the person.
`roles.<role>.agent`	An agent: system prompt, tools, confirmation policy.
`roles.<role>.model`	A LiteLLM alias (`frontier`, `fast`, `open-coder`, ...).
`roles.<role>.vm`	A profile: image, vCPUs, memory, disk.
`replicas.max`, `concurrent_runs`	How far a role scales out and how many runs one replica takes.
`sleep`	Idle time before an agent is snapshotted and the time before deep sleep.
`budget_usd_per_day`	The default daily budget of teams made from it.
`isolation`	`shared` or `dedicated`, see team isolation.
`rework_rounds`	Review-and-fix cycles per work item.
`pipeline`	The fixed hand-off chain.

Templates live in the control-plane database. A fresh database is filled from teams/templates/*.yaml by the importer, and just console-export writes them back as files. Read them with GET /team-templates; admins change them from the Console or with POST /team-templates/{name}/versions. A template that needs a repository refuses POST /teams without repo_url.

Depth: architecture, Templates.