Use cases
Start everything at once.
Auth, schema, UI shell, tests, CI, and docs do not have to queue behind each other. One brief becomes a mission, and six real Claude Code sessions build the skeleton in parallel.
One brief
The whole skeleton from one paragraph.
Type the goal once. The Conductor plans it into a DAG of tasks, holds the order where pieces depend on each other, and lets everything else run side by side. It watches every terminal, answers permission prompts, and verifies each piece before the mission moves on. If you have never run one, start with your first goal.
# day one, six lanes
New SaaS starter: email auth, Postgres
schema and migrations, React shell with
routing, integration tests, GitHub
Actions CI, and a README that matches
what actually exists.The fleet
Watch it assemble.
Parallel by default
Independent pieces start immediately. The schema does not wait for the UI shell, and the docs are written against code that already exists by the time that task runs.
Steer anytime
The mission DAG and live activity strips show what every terminal is doing. Each session is a real Claude Code TUI, so you can open one and type when you want a say.
Verified before done
Every task is re-checked before it counts. A session that declares victory early gets caught, and a session that stalls or exits is recovered and re-sent its task.
In the workspace
From empty folder to running app.
Design first
If the project has a face, the Design tab is a website builder that designs before it builds: theme first, then a page plan, then the fleet builds it.
See it run
Dev servers are auto-detected and opened in an inline web preview, so the first successful boot of the app shows up inside Loom, not in another window.
Review it all
The source control panel shows a full git graph of what six sessions produced. Read every diff before anything is pushed. See reviewing fleet work.
Hand it the work.
Walk away.
macOS, Linux, and Windows. Around 13 MB. Free and open source.