The default team
The first run gives you a team of four, so you can start work before writing a team package. Each agent has one job, a ceiling on what it may do, and one thing it cannot do.
| Agent | Its job | Mode | It cannot |
|---|---|---|---|
| Chief of staff | Your point of contact. Does what you ask, and hands work to the right teammate | accept-edits | Merge a pull request |
| Planning Lead | Turns a goal into tasks small enough for one agent each | plan | Write any code itself |
| Builder | Builds one task in its own worktree and opens a pull request | accept-edits | Merge it |
| Reviewer | Reads the pull request and posts findings with a recommendation | plan | Approve it |
No agent on any team can merge. A person merges.
When a task finishes
A finished task stops before it pushes and waits in the Inbox, because the approval mode starts at
ask. lucitra approval-mode auto, or Settings → Approvals, lets tasks push and open their pull
requests on their own. The default team has no policy file, so in auto nothing on it holds a push.
Change an agent
lucitra agents # the team, and what each agent is set to do
lucitra models # which model each agent runs, on which runtime
lucitra configure reviewer runtime codex # one setting on one agent
lucitra reset reviewer runtime # back to the default
Any agent can take a name and a face on this machine: lucitra set-identity default/reviewer nickname Rosa, or Name and photo on its page in the app. The role always shows beside the name,
so "the Reviewer approved this" means the same thing on every install. The name stays on your
machine; runs are told it, and routing and permissions keep the role.
Modes
| Mode | The agent may | It stops for |
|---|---|---|
plan | Read and analyze, and produce a plan | Everything. It never writes |
manual | Read | Every write and every command |
accept-edits | Read, write and commit inside its own worktree | Commands outside its allowlist, and anything beyond the repository |
auto | Work without asking; its tool policy still applies | Anything outside the repository |
bypass | Work with its tool policy off | Nothing. Merge is still out of reach |
A mode is a ceiling: a task can narrow an agent's mode, never widen it. Pushing at the end of a task
is not a mode's decision. It follows your approval mode, and in auto the team's policy, as above. See
Runtimes for how each runtime enforces the ceiling.