ucitra/ agent teams

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.

AgentIts jobModeIt cannot
Chief of staffYour point of contact. Does what you ask, and hands work to the right teammateaccept-editsMerge a pull request
Planning LeadTurns a goal into tasks small enough for one agent eachplanWrite any code itself
BuilderBuilds one task in its own worktree and opens a pull requestaccept-editsMerge it
ReviewerReads the pull request and posts findings with a recommendationplanApprove 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

ModeThe agent mayIt stops for
planRead and analyze, and produce a planEverything. It never writes
manualReadEvery write and every command
accept-editsRead, write and commit inside its own worktreeCommands outside its allowlist, and anything beyond the repository
autoWork without asking; its tool policy still appliesAnything outside the repository
bypassWork with its tool policy offNothing. 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.

Cookie settings

Choose what this site may store in your browser. You can change it any time from Cookie settings at the bottom of every page.

EssentialAlways on

Remembers the choice you make here. Nothing else is stored until you turn analytics on.

What is stored
NameWherePurposeKept
lucitra-consentLocal storageYour analytics choiceUntil you clear it
Analytics

Shows us which pages people read, what breaks, and which links bring people here, so we know what to fix. Off until you turn it on.

What is stored
NameWherePurposeKept
ph_<key>_posthogCookieA random identifier for your browser, and the current session1 year
ph_<key>_posthogLocal storageThe same identifier, as a backup to the cookieUntil you clear it
lucitra-last-touchSession storageThe link or campaign that started this visit, sent only with a contact form messageUntil you close the tab
lucitra-first-touchLocal storageThe link or campaign of your first visitUntil you clear it
lucitra-last-touchLocal storageThe link or campaign of your latest visitUntil you clear it
Cookie policy