MAESTRO Get started
How it works

The thirteen phases of a mission

You give MAESTRO a task and a repository. What happens next is a fixed sequence, with one place where it stops and waits for you.

Most coding agents are a loop: read the task, edit files, run something, report. MAESTRO is a pipeline. Each phase has one job, writes down what it did, and hands over. The point of the structure is not ceremony — it is that a phase which cannot do its job has somewhere to say so, instead of passing an unchecked result to the next step as though it were checked.

Before anything is written

Why the stop is here

The approval gate sits after the plan and before the edit because that is the last moment at which disagreeing with the agent is cheap. Once an executor has run, reviewing its work means reading a diff; before it runs, it means reading a paragraph.

Writing the code

Afterwards

What runs the code, and what argues about it

A mission uses exactly one executor, chosen per mission: Codex (gpt-5.4, the default) or Claude (claude-opus-4-6). The planning phases are deliberately not the same model as each other — a proposer, two challengers and a synthesis step drawn from different model families — because a debate in which every participant shares the same blind spot is not a debate.

The research those phases do is not generic retrieval. Every function, class, method and import relationship in the repository is parsed with Tree-sitter into a structural graph, which can be asked who calls this, what depends on it, and what breaks if it changes. Alongside it runs a full-text BM25 search over every symbol, and the two result sets are fused. There is no embedding model and no vector search anywhere in the system: retrieval is lexical and structural, which makes it fast, deterministic and explainable. The structural graph currently parses Python, TypeScript, JavaScript, Java and Go; other languages are searched lexically and run in the sandbox, but are not graphed.

Outcomes are kept per project. What was attempted, what failed and what was learned on earlier missions is retrieved into the debate on later ones, so the system's knowledge of your repository accumulates rather than resetting each time.

The part most agents skip

A pipeline is only worth the phases that can say no. Three of them can: spec_validation refuses a plan that does not match the repository, safety refuses a diff that does something destructive, and commit_or_retry refuses a change that broke a test that used to pass. And when the test suite could not be run at all — no runner in the sandbox, a suite that collected nothing, output the parser could not read — the mission does not quietly report success. It completes with the status completed_unverified, and the record carries the reason.

That is the whole argument for the structure. What the record contains and how the sandbox is isolated are each worth their own page.