// supervisor

One supervisor. Every agent reports to it.

The Supervisor is an AI agent whose whole job is running other agents. You brief it in plain English; it plans, delegates, reviews, and merges — and never touches your code itself.

§ 01

An agent that runs agents

The Supervisor is a real LLM with the same memory and tools as the agents it dispatches — but a different prompt and a different scope. Its job is not to write code. Its job is to decide what gets built, by whom, and in what order.

supervisor
model claude-opus-4-8
role supervisor
scope agent orchestration
spawn builder-4a · feat/oauth
spawn scout-2b · scout/routes

You steer it the way you would steer a tech lead: a goal, a constraint, a correction. It handles the decomposition.

§ 02

Five roles, or write your own

Every agent runs a role — a system prompt plus a tool allow-list. Five ship built in; you can author more as markdown files committed alongside your code.

roles
supervisor plans, dispatches, reviews, merges
builder implements features and fixes, writes tests
scout surveys the codebase, writes findings to memory
reviewer reads a diff, approves or requests changes
coordinator watches a milestone end to end
Note

Custom roles live in .zevyn/roles/<name>.md — version-controlled with your repo, shared with your team.

§ 03

You stay in command

The Supervisor proposes; you dispose. It shows you its plan before spawning anything, streams every agent's terminal as they work, and asks before anything destructive. Nothing reaches your main branch without a decision from you.

  • Plain-language briefs — no config files, no DSL to learn.
  • Every agent's live terminal output streamed back to you.
  • Approve, redirect, or kill any agent at any point.
// related

Stop supervising one agent.

Zevyn Studio is launching soon. Join the waitlist and start directing a team.