maestro

Maestro is a local-first conductor for multi-agent software engineering. It gives you one CLI and one on-disk state model for missions, features, assertions, handoff launches, checkpoints, memory, and project context so separate agent sessions can collaborate without a server, database, or background daemon.

It is designed for a workflow where a human operator coordinates multiple terminals, while Maestro keeps the shared state disciplined and inspectable.

Maestro is the shared state layer in the middle. The operator and fresh agent runs both go through the CLI, the CLI persists shared state locally, and Mission Control projects that same state without mutating it.

• Shared state lives on disk in .maestro/, not in chat history.
• Missions break work into milestones, features, and validation assertions.
• Native handoff launches build a self-contained markdown brief and start a fresh Codex or Claude run from the current repo state.
• Memory commands turn corrections and learnings into reusable guidance.
• Mission Control gives you a read-only TUI and JSON snapshots of current state.
• The runtime stays local-first: filesystem, git, config, and terminal tools.
• It is not a hosted orchestration service or remote agent platform.
• It is not tied to a single model vendor or harness.