Skip to content
Docs0.9GitHubInstall

GuidesLeads and teams

Run recurring work with leads and teams

Declare a chief, leads, and their members in one project file, add a Monday schedule, and hear from one agent.

This guide sets up agents that always run, arranged as a teamTeam. The agents a manager leads. Teams nest, and an agent may have several managers. that reports to you through one of them. The structure lives in a project fileProject file. A vendetta.toml at a project's root that declares agents that always run, their teams, and schedules., so it is versioned with the work.

The examples follow Ilya, who runs a two-person company selling a booking tool. The project is northwind.

Put a vendetta.toml at the root of the project’s git repository:

~/projects/northwind/vendetta.toml
[agents.chief]
name = "Chief of staff"
manager = true
brief = """
You run Northwind's recurring work through three leads. Collect their reports,
tell me what needs a decision, and keep the rest moving.
"""

[agents.eng]
name = "Engineering lead"
manager = "chief"
brief = "You lead engineering for the booking tool. Your team is the backend agent."

[agents.backend]
name = "Backend"
manager = "eng"
brief = "You own the booking API in api/."

[agents.growth]
name = "Growth lead"
manager = "chief"
brief = "You own pricing and the landing page."

[agents.support]
name = "Support lead"
manager = "chief"
brief = "You triage the support inbox."

[schedules.monday]
cron = "0 8 * * 1"
timezone = "Europe/Berlin"
agent = "chief"
prompt = "Collect last week's work from each lead and report."

Each [agents.ID] is a declared agentDeclared agent. An agent a project file names. Vendetta starts it and resumes it whenever it exits.Declared agent. An agent a project file names. Vendetta starts it and resumes it whenever it exits.: one that always runs. Vendetta starts it with its brief as its first prompt and resumes the same conversation whenever it exits. Without provider, an agent runs on [harnesses] default; omp, Codex, and Claude Code can be declared.

manager = true makes an agent a managerManager. A Master for part of the work, usually one project: an agent with a team beneath it.Manager. A Master for part of the work, usually one project: an agent with a team beneath it.. manager = "chief" puts an agent in the chief’s team, mutedMuted. An agent whose turns, questions, and approvals notify nobody.Muted. An agent whose turns, questions, and approvals notify nobody., so its news goes to the chief.

Teams nest to any depth and may not form a cycle. A file holds up to 32 agents and 64 schedules.

Nothing in the file runs until you trustTrust. Your approval of a folder's project file. Nothing in the file runs before it.Trust. Your approval of a folder's project file. Nothing in the file runs before it. its folder. Only you can, from the app or the chooser; an agent, the Master, a schedule, and a shell cannot.

Vendetta finds the file once the project is known to it: a tmux session in that folder, or an agent that runs or ran there. Check what it found:

vendetta project status
  • Web client: open the project. A card for the file says nothing in it runs until you trust the folder. Choose Trust, read the agents and schedules it lists, and confirm with Trust folder.
  • iPhone: open the project, find its vendetta.toml section, and tap Trust.
  • Chooser: select the project and press A.

The agents start a few at a time. Later edits to agents and schedules you trusted apply without asking. An agent or schedule the file adds afterwards waits for your approval, so a git pull can’t add work that runs unasked.

The chief appears with its team beneath it, and each lead with its own members beneath that. In the overview, each card names its team: Manages N, or its manager. Fold a team under its manager to shorten the list; folded, it still marks a member that waits on a question or an approval.

Members are muted. Their finished turns, questions, and errors reach their manager, and the manager tells you what matters, with links that open the member’s exact reply.

The monday schedule prompts the chief at 08:00 on Mondays. The chief asks its leads, and you get one report. A link in it opens the lead’s chat at the reply it refers to.

File schedules show on the schedules screen, where you can pause one, run it now, and acknowledge a failed run. To change one, edit the file. A run while the chief is paused or failed fails and is not retried.

A schedule with no cron or at runs only on demand: by Run now, or by a webhook. Add one for support triage and point a hook at it:

[schedules.triage]
agent = "support"
prompt = "New support mail arrived. Triage it and report what needs me."

The hook names the schedule by its ID, which for a file schedule starts with file-; vendetta schedule list shows it.

Ask a lead for a comparison and it can answer with a page: three pricing options side by side, with a button for each. Open it in the chat, pick one, and the page sends your choice to the agent as a message. See A checklist page you reuse.

With a Master configured, Talk to Master starts a hands-free conversation in the app: it sends when you pause, reads the reply aloud, and listens again. The Master can list and read every agent, so “what is engineering blocked on?” is a question for it.

Declared agents are started by Vendetta, so on your computer they ask before they run commands. An approvalApproval. A provider's permission dialog for a tool call. Only you answer one: at the terminal, or for Claude Code in the iPhone and web apps with Allow once or Deny. is never answered by a manager, the Master, or a schedule. It waits for you in the app’s Needs you lane and at the agent’s terminal. A muted member’s approval is reported to its manager, whose job is to tell you.

  • Stopping a declared agent from the app or the chooser pauses it until you start it again. Typing /exit in its terminal does not: Vendetta resumes it.
  • Renaming happens in the file.
  • Model and effort come from the file (model, effort). A member without them takes its manager’s team choices, then [harnesses.PROVIDER] team.
  • An agent that keeps exiting soon after it starts is marked failed, and you are told. It waits for you to start it.

With many agents on one login, watch your plan’s limits. See Usage and context for where each app shows them.

The full format is in Project file.