Maestro 🤖 Agent Open source

What it does

Maestro is a multi-agent development orchestration platform. Given a task, it classifies the work, chooses between a lightweight Express path and a four-phase Standard workflow (design, plan, execute, complete) with explicit approval gates, asks the required design questions, produces an implementation plan when needed, delegates execution to specialists, runs a quality gate, and archives the session state. It also offers standalone audits for review, debugging, security, performance, SEO, accessibility, and compliance.

What is inside

The platform ships 39 specialist agents plus orchestration commands, generated from a canonical source and packaged per runtime. A shared command surface covers orchestrate, execute, resume, status, archive, review, debug, security-audit, perf-check, seo-audit, a11y-audit, and compliance-check, with runtime-specific names to avoid colliding with host commands. Persistent session, plan, and archive outputs are written under a configurable state directory (docs/maestro by default). Environment variables tune execution mode, auto-archiving, retry limits, parallel-agent caps, and which specialists are disabled. A Standard run succeeds only with an approved plan, completed phase reports, validation for the changed surface, and no unresolved Critical or Major review findings.

Works with

Claude Code, Codex, and Gemini CLI (the project also supports Qwen Code). It installs as a Gemini or Qwen extension, a Claude Code plugin, or a Codex plugin, and Node.js 20 or higher is needed for the MCP server and helper scripts.

How to install

claude plugin marketplace add josstei/maestro-orchestrate
claude plugin install maestro@maestro-orchestrator --scope user

Maintenance and safety

Apache-2.0 licensed and actively maintained, with unit, transform, and integration tests and release artifact verification. Maestro follows the host runtime's tool permissions, sandboxing, and confirmation model, requires no committed secrets or long-lived credentials, and keeps session state inside its state directory.

Who should use it

Developers who want a structured, gated orchestration layer with a large specialist bench that works the same way across several coding agents.