Worker agents
Optional bounded delegation, with the coordinator integrating the result.
Four roles
| Role | Responsibility |
|---|---|
| Explorer | Answers a narrow codebase question with evidence. |
| Planner | Investigates an approved intent and proposes a plan shape. |
| Worker | Implements an assigned plan or slice and runs normal checks. |
| Reviewer | Independently reviews a diff read-only, only on a person's request. |
The host runs the agent
The CLI returns a dispatch specification containing the working directory, ownership, record, assignment, and required return. It does not launch a model or hold model credentials. The coordinator invokes host tools, waits, and integrates results.
Shared model and effort preferences live in role configuration; local overrides stay on the machine. Defaults inherit host settings. agent setup writes ignored native definitions; the host may need to reload them.
Delegate when it helps
Small tasks can stay with the coordinator. Workers sharing a worktree must preserve one another's edits. Dispatch is not completion evidence, and an implementation check is not independent review.
Roles authorize nothing
An agent role, like a member's recorded role in members.yaml, says what someone contributes. It grants no permission: no agent message is a person's consent, and only a person approves, authorizes delivery, or agrees to a deletion.
No attribution
Commits, pull requests, reviews, and comments carry no agent attribution, credit, co-author, or generated-by text. agent setup turns Claude Code's commit and pull request attribution off in the gitignored .claude/settings.local.json. Codex has no such setting, and Cursor reads it only from a person's own or a team admin's configuration, so there the written rule is the guard and the agent inspects each commit message before reporting delivery.