Skip to main content
Workers are agent identities with a role. The CTO can use them for focused tasks such as implementation, testing, review, or documentation.

What a worker has

FieldMeaning
NameHuman-readable identity, such as test-writer.
RoleWhat kind of work the worker should do.
Provider and modelHow the worker runs.
BudgetMonthly spend or usage boundary for that worker.
ActivityRecent tasks, sessions, and outcomes.

When workers help

  • A task should be split into several lane-scoped parts.
  • You want a repeatable role, such as tester or reviewer.
  • You need project-level coordination but focused execution.
  • You want budget and activity visibility by responsibility.

Basic flow

1

Ask the CTO for a plan

Describe the goal and ask how it should be split.
2

Approve the shape

Confirm lanes, worker roles, and validation expectations.
3

Let workers execute

Watch active lanes and sessions from Work, Lanes, and History.
4

Review the output

Inspect diffs, tests, proof, and PRs before merging.
Workers are still coding agents. Review their output like any other contribution.