Repository navigation
v0.1.0
The first public release of maestro: coding agents, orchestrated as code. Compose agents, checks and reviews into a
typed graph, have maestro check it and bound its spend before any model call, perform it in isolated lanes, and get back
a changeset you decide whether to apply.
Install
maestro runs on Linux x64 with glibc, and needs bubblewrap, bash, git 2.40 or newer, and a harness: Claude Code 2.1.318
or pi 1.5.0.
curl -fsSL https://raw.githubusercontent.com/dvalnn/maestro/next/install.sh | shTo pin this release, put MAESTRO_VERSION=v0.1.0 before sh. The script checks every asset against SHA256SUMS,
warns of each missing requirement and harness at another version, and logs what it changes. Full requirements, the
config to write first and manual steps are in INSTALL.md.
What's in it
Compose. A composition is a typed TypeScript function from params to a graph of agents, checks, code nodes, loops,
fan-outs and subcompositions. maestro compose builds and checks it, spending nothing: types, config, profiles and an
upper bound on node instances and agent runs. --plan shows that bound and which profile, harness and model each seat
gets, and --graph prints it as a Mermaid flowchart. A plan past a configured cap is refused.
Perform. maestro perform runs the graph as a concert. Each agent and check works in a lane, a versioned working copy
cut from your repository, inside a bubblewrap sandbox; your checkout is never touched. Every step is recorded, so
resume continues a failed or rejected concert where it stopped and encore runs one again with new params. --detach
starts a concert in the background.
Apply. A concert's way out is its changeset: maestro cs show prints the patches, cs apply lands them on your
checkout, as a commit with --commit, and cs drop resets an applied change you decide against.
Follow. watch shows a concert live, wait blocks until it settles, ls lists concerts or one concert's node
instances, artifact shows what each node left, kill stops one and prune deletes settled ones. Every read command
takes --json, and long output pages on a terminal.
Profiles and config. A seat names a profile: a directory with the runtime (harness, model, thinking), instructions,
attachments, limits and context policy an agent runs with. A profile's harness extras bring the harness's own settings,
hooks, plugins, extensions or model catalogue. Config layers user and workspace files, presets and -c overrides;
maestro config and maestro agent show name the layer behind each value, and agent probe checks a profile against
its harness. --preset stub swaps every agent for one that changes nothing, to rehearse a composition for free.
Harnesses. Claude Code and pi, chosen per profile, so a reviewer from one model family can be challenged by a skeptic
from another.
The classics pack. Ready-made compositions: build_then_repair builds a request test-first and repairs it until your
checks pass, repair_until_green repairs a lane while its checks are red, and panel_review reviews a change through
lenses, a skeptic over each lens's findings and a consolidator.
Skills. A maestro skill, and a maestro-ultracode skill that drives each task through a composition written for
it, installed for Claude Code, Codex and pi.
Assets
| Asset | Holds |
|---|---|
install.sh |
The install script |
maestro-linux-x64.gz |
The standalone binary, gzipped |
classics-0.1.0.tar.gz |
The classics pack |
maestro-skill.tar.gz |
The skills |
maestro-<package>-0.1.0.tgz1 |
Package tarballs for writing compositions |
harnesses |
The harness versions this release supports |
SHA256SUMS |
Checksums of every asset |
Documentation
README for a quick start, the
classics pack, the
CLI beyond maestro <verb> --help, and the
SDK spec for writing compositions.
maestro is MIT-licensed.
-
ir,sdk,host-repo-sdkandclassics. ↩