> ## Documentation Index
> Fetch the complete documentation index at: https://ade-ac1c6011-dependabot-github-actions-actions-cache-6.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Workers
> Workers are named agent identities the CTO delegates scoped work to — each with a role, model, budget, and activity history, running in its own lane.
**Workers** are named agent identities that the CTO can wake for delegated work. The CTO owns the team; each worker runs inside a lane with its own role, model settings, budget, and activity history. When the CTO splits a plan into lane-sized tasks, it hands each task to a worker, and they run in parallel under the CTO's coordination.
## What a worker has
| Field | Meaning |
| --------------- | ------------------------------------------------------------------------------------------------------------------ |
| Name & role | A human-readable identity (e.g. `test-writer`) and a role: engineer, QA, designer, devops, researcher, or general. |
| Adapter & model | How the worker runs and which model it uses. |
| Budget | A soft monthly spend cap, tracked per worker and across the team. |
| Heartbeat | Whether the worker stays running or wakes only when called. |
| Activity | Recent runs, sessions, and outcomes in its feed. |
## Create a worker
The Team tab's two-step wizard makes adding a worker quick.
Start from a template — backend engineer, frontend engineer, QA tester, devops, researcher, or custom. Each seeds a sensible role and capabilities.
Set the name, role, capabilities, model, and a monthly budget. Save persists the identity and records a config revision.
Worker config is strict about secrets: raw API keys are rejected. Reference secrets as `${env:VAR_NAME}` so credentials never land in a saved worker config.
## Adapters
A worker dispatches through exactly one of three adapter types. Anything that wraps an external runtime does so as a `process` adapter — there are no other types.
Spawns the Claude CLI locally.
Spawns the Codex CLI locally.
A generic managed subprocess for a long-lived or out-of-tree worker runtime.
## Budgets and heartbeats
Each worker has a monthly cap tracked per worker and across the team. Nothing blocks execution when a cap is hit — the UI surfaces a warning chip so you can step in.
A worker with a heartbeat stays "always running"; with it off, the worker only comes to life when the CTO wakes it or a Linear workflow dispatches to it.
## Basic flow
Describe the goal and ask how it should be split.
Confirm lanes, worker roles, and validation expectations.
Each worker runs in its own lane. Watch active sessions and runs from Work, Lanes, and History.
Inspect diffs, tests, proof, and PRs before merging.
Workers are still coding agents. Review their output like any other contribution — nothing merges without your review.
How the project-level operator plans and delegates.
Patterns for splitting work cleanly across agents.