MAESTROMAESTRO
An AI that conducts other AIs. The most capable model plans and delegates; cheaper models execute; a fresh judge and a plain script decide what ships. Nothing goes out unattended.
The loop: nothing is done until the gate says so
Why it's different
Careful because it's autonomous
A constitution of hard laws, a deterministic gate that holds the final vote, and sensitive work that queues for a human instead of guessing.
It has run itself
Given a real task, it scouted, planned, built, verified, and gated the change end to end, and shipped nothing unattended.
Runs on any machine
Clone it, run one command, point it at your own repo. Standard library only. No lock-in, no service to sign up for.
Free and open
Built on the public OsmoSync method, adopted not reinvented. You get the whole thing to run and adapt.
What you get
Sign up and you receive the whole thing, ready to run. Not a waitlist for a product, the actual working system.
A repo you clone and keep
The public maestro-starter repo, yours to clone. The code lives on your machine, not behind a login you have to maintain.
The four-party loop, wired up
Triage, Conduct, Build, Verify, then a deterministic gate, then a human ships. It arrives assembled, not as a diagram you build yourself.
A kickoff prompt to paste
One prompt that puts the conductor to work. Copy it, paste it into Claude Code, and the loop starts on your first task.
A plain README
A short read that takes you from zero to conducting. No jargon, no setup maze, no video course to sit through.
Standard library only
No service to sign up for, no dependency to install, no vendor to trust. Run it, read every line, change what you want.
How to start in three steps
Clone and bootstrap
Clone the repo and run one bootstrap command. That is the whole install, no extra tooling to chase down.
Paste the kickoff prompt
Drop the kickoff prompt into Claude Code. The conductor wakes up, takes the brief, and calls the loop.
Point it at your repo
Aim it at your own project and approve what ships. A human signs off on every change before it lands.
What it is, and isn't
MAESTRO is a disciplined autonomous orchestrator, adopted from the public OsmoSync method, not a magic box. It plans, builds, and checks its own work, and a human still approves every ship.
Get early access
Drop your email and I'll send you MAESTRO the moment it's packaged to install: the repo, the setup, and the exact prompt to start conducting.