Maestro Orchestrate
Maestro is a multi-agent development orchestration platform with 39 specialists, offering an Express path for simple tasks and a 4-phase standard workflow for complex ones. It runs across Gemini CLI, Claude Code, Codex, and Qwen Code, providing persistent session state and standalone review, debug, security, performance, SEO, accessibility, and compliance entrypoints. It is for developers who want to delegate coding tasks to specialized agents within their preferred AI coding runtime.
✨ Key features
- 39 specialist agents for diverse development tasks
- Express workflow for simple tasks with minimal questions
- Standard 4-phase workflow (Design, Plan, Execute, Complete) with approval gates
- Persistent session state and archiving under docs/maestro
- Standalone commands for review, debug, security, perf, SEO, a11y, compliance
- Runs across Gemini CLI, Claude Code, Codex, and Qwen Code
🎯 Use cases
- Orchestrate building a REST API with authentication
- Run a standalone code review on staged changes
- Perform a security audit on authentication and data exposure
- Resume a previous orchestration session
- Check code for performance, SEO, accessibility, or compliance issues
📦 Installation
🧰 Requirements: Requires one supported runtime (Gemini CLI, Claude Code, Codex, or Qwen Code) and Node.js 20+ for the MCP server and helper scripts. For Gemini CLI and Qwen Code, enable experimental subagents in settings.json.
Gemini CLI
gemini extensions install https://github.com/josstei/maestro-orchestrate
Local development:
git clone https://github.com/josstei/maestro-orchestrate
cd maestro-orchestrate
gemini extensions link .
Claude Code
Marketplace install:
claude plugin marketplace add josstei/maestro-orchestrate
claude plugin install maestro@maestro-orchestrator --scope user
Codex
Register the marketplace:
codex plugin marketplace add josstei/maestro-orchestrate
Then start Codex, run /plugins, select Maestro, and choose Install.
Qwen Code
qwen extensions install https://github.com/josstei/maestro-orchestrate
🚀 Usage
Start a full orchestration with the runtime-specific entrypoint:
| Runtime | Example |
|---|---|
| Gemini CLI | /maestro:orchestrate Build a REST API for a task management system with user authentication |
| Claude Code | /orchestrate Build a REST API for a task management system with user authentication |
| Codex | $maestro:orchestrate Build a REST API for a task management system with user authentication |
| Qwen Code | /maestro:orchestrate Build a REST API for a task management system with user authentication |
⚠️ Good to know
Maestro does not edit settings files for you; you must enable experimental subagents manually for Gemini CLI and Qwen Code. Also, for Claude Code and Codex, some command names are intentionally different to avoid collisions with host commands.
❓ FAQ
What runtimes does Maestro support?
Maestro supports Gemini CLI, Claude Code, Codex, and Qwen Code, with a canonical source tree that generates runtime-specific files.
How do I enable experimental subagents for Gemini CLI or Qwen Code?
You need to manually edit ~/.gemini/settings.json or ~/.qwen/settings.json to include {"experimental": {"enableAgents": true}}.
What is the difference between Express and Standard workflows?
Express is for simple tasks with 1-2 clarifying questions and no design doc. Standard is for medium/complex tasks with Design, Plan, Execute, and Complete phases and approval gates.
Where does Maestro store session state?
Session state is stored under MAESTRO_STATE_DIR, which defaults to docs/maestro.
📊 Repository
🤖 Overview, features, install steps and FAQ were generated from the project's README on Sep 4, 2026. Always check the original source before running commands.