One person.
A whole
fleet of agents.

Not screenshots and not a mock-up: every screen on this page is rebuilt in the browser at the device's real point sizes, from the SwiftUI source. The Mac window is 1000 × 620 pt on a 16-inch display; the phone is an iPhone 393 × 852.

A .NET backend on one Mac, clients on macOS, iPhone, iPad and Apple Watch, and a SignalR connection carrying every agent's output live to all of them.

Nothing here is faked. Where a control does not exist in the app, it is not drawn.

You do not create a group, then an application, then features, then tasks. You write what you want. The orchestrator names it, builds the tree, provisions the repo and spawns a lead agent that decomposes the rest.

“Conductor decides” lets it work out how many workers the build needs. Set a maximum instead and it will not exceed it — the cap is 8.

The model is not a choice here on purpose: the field is left off the request so the backend always uses its current default.

Group, application, feature, task, agent. An agent is never “running somewhere” — it is bound to a task, under a feature, inside an app. That is what makes eight of them at once survivable.

Pick a feature and its tasks unfold underneath it, with the agents on each task one level deeper again.

A task that has finished waits at awaiting_review with an accept and a reject button right there in the tree.

Pick a scope and the map filters to the agents inside it. The crown is the lead — the one that decomposed the work and can be told to change course. Everything under it is a child it spawned.

The ring around each agent is the supervisor talking: solid for running, orange dashed for “this one has stopped moving”, red dashed for “a cascade kill has accepted it”. The pill on the right is how much of its context window is gone.

The map is four columns — groups, applications, features, agents — because a fleet with no addresses is a fleet you cannot steer.

A Claude Code session is not one pipe of text — it is typed events. Conductor keeps the type on every line and gives you a switch per type, so “show me only the errors and what it decided” is one menu, not a grep.

The field at the bottom talks to the agent that is running, mid-run. On a lead it is a conversation; on a worker it is a one-off intervention, and the app labels it as such.

Seven types, seven colours — the same seven TerminalPaneView defines. Try switching them off.

The detail column is a docking host, not a terminal. Every leaf has its own tab bar, every tab is one of eight kinds, and any pane splits right or down — so three agents, a shell and the link map can all be on screen while they work.

⌘\ splits right, ⌘⇧\ splits down, ⌘` walks the panes. The tabs drag between them.

With the gate on, a task whose agents are done does not complete. It parks at awaiting_review and shows up here, fleet-wide, with the diff it produced and the result of building it.

Accept and the task completes. Reject and it goes back to in-progress with your note attached, so the agent knows what to change.

The order on the card is deliberate: what it claims, what to test, whether it built — and only then the Accept button.

Pending decisions, tool approvals nobody has answered, agents that errored, constraint violations, tasks waiting on review — five different tables in the backend, one ranked list in front of you.

⌘⇧A anywhere in the app. The toolbar button carries the count, so an empty inbox is visible without opening it.

The backend is headless by design — it lives on a Mac that need not have anyone in front of it. So the phone is not a viewer: it is the control surface, with a real VT terminal attached to the live session and a key bar for the things an iOS keyboard has no key for.

Four tabs, because the design rules cap it at four: Sessions, Decisions, Dashboard, More.

The second tab was called Inbox once. It was renamed to Decisions, because that is what is in it.

When an agent hits a fork it cannot take alone, it stops and asks — and the question arrives as a time-sensitive push, not a line in a log you were not reading.

A destructive option is styled as one. “Deny”, “Drop”, “Stop”, “Cancel” and “Reject” get the destructive treatment automatically, so the dangerous button never looks like the safe one.

Answer it and the agent picks up where it stopped. Two taps, from a phone, with the Mac at home.

Not an aggregate “3 agents running” — one Activity per agent, so the one you are watching is the one on your screen. It carries the status, the tool it is in right now, and the feature's own colour.

When it needs approval the Activity says so, and the push that carries it is marked time-sensitive so it comes through a Focus.

Tap the pill to open the agent. Long-press expands it — that is what the Expand chip does here.