Maestro is a multi-agent development orchestration platform with 39 specialists, an Express path for simple work, a 4-phase standard workflow for medium and complex work, persistent session state, and standalone review/debug/security/perf/seo/accessibility/compliance entrypoints. It runs from one canonical src/ tree across Gemini CLI, Claude Code, Codex, and Qwen Code.
| Runtime | Location | Public Surface | Notes |
|---|---|---|---|
| Gemini CLI | repo root | /maestro:* |
Snake-case agents, TOML commands, hooks, TOML shell policies |
| Claude Code | claude/ |
/orchestrate, /review, ... |
Kebab-case agents with maestro: subagent names |
| Codex | plugins/maestro/ |
$maestro:* |
Plugin skills, spawn_agent, no runtime hooks |
| Qwen Code | qwen/ |
/maestro:* |
Gemini-CLI-compatible extension, QWEN.md context file, SubagentStart/SubagentStop hooks |
- One supported runtime: Gemini CLI, Claude Code, Codex, or Qwen Code
- Node.js 18+ for the MCP server and helper scripts
- Gemini CLI and Qwen Code only: enable experimental subagents in
~/.gemini/settings.json(Gemini) or~/.qwen/settings.json(Qwen)
{
"experimental": {
"enableAgents": true
}
}Maestro does not edit ~/.gemini/settings.json or ~/.qwen/settings.json for you.
gemini extensions install https://github.com/josstei/maestro-orchestrateLocal development:
git clone https://github.com/josstei/maestro-orchestrate
cd maestro-orchestrate
gemini extensions link .Verify with gemini extensions list.
Marketplace install:
claude plugin marketplace add josstei/maestro-orchestrate
claude plugin install maestro@maestro-orchestrator --scope userDevelopment / temporary loading:
git clone https://github.com/josstei/maestro-orchestrate
claude --plugin-dir /path/to/maestro-orchestrate/claudeMore Claude-specific setup and plugin management lives in claude/README.md.
codex marketplace add josstei/maestro-orchestrateThen start Codex, run /plugins, and select Maestro â Install.
Local development:
git clone https://github.com/josstei/maestro-orchestrate
codex marketplace add /path/to/maestro-orchestrateMore Codex-specific setup and runtime details live in plugins/maestro/README.md and docs/runtime-codex.md.
qwen extensions install https://github.com/josstei/maestro-orchestrateLocal development:
git clone https://github.com/josstei/maestro-orchestrate
cd maestro-orchestrate
qwen extensions link .Verify with qwen extensions list. Qwen Code uses the same /maestro:* command surface as Gemini CLI and reads QWEN.md as its context file.
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 |
Maestro classifies the task, chooses Express or Standard workflow, asks the required design questions, produces an implementation plan when needed, delegates execution to specialists, runs a quality gate, and archives the session state in docs/maestro/.
| Capability | Gemini CLI | Claude Code | Codex |
|---|---|---|---|
| Orchestrate | /maestro:orchestrate |
/orchestrate |
$maestro:orchestrate |
| Execute | /maestro:execute |
/execute |
$maestro:execute |
| Resume | /maestro:resume |
/resume |
$maestro:resume-session |
| Status | /maestro:status |
/status |
$maestro:status |
| Archive | /maestro:archive |
/archive |
$maestro:archive |
| Review | /maestro:review |
/review |
$maestro:review-code |
| Debug | /maestro:debug |
/debug |
$maestro:debug-workflow |
| Security Audit | /maestro:security-audit |
/security-audit |
$maestro:security-audit |
| Performance Check | /maestro:perf-check |
/perf-check |
$maestro:perf-check |
| SEO Audit | /maestro:seo-audit |
/seo-audit |
$maestro:seo-audit |
| Accessibility Audit | /maestro:a11y-audit |
/a11y-audit |
$maestro:a11y-audit |
| Compliance Check | /maestro:compliance-check |
/compliance-check |
$maestro:compliance-check |
For Codex, Maestro intentionally avoids bare skill names that collide with host commands. Use $maestro:review-code, $maestro:debug-workflow, and $maestro:resume-session so Codex's built-in /review, /debug, and /resume commands keep working.
Qwen Code uses the same /maestro:* command surface as Gemini CLI.
- Express: For simple work. Maestro asks 1-2 clarifying questions, proposes a brief, delegates to one specialist, runs code review, and archives without a design doc or implementation plan.
- Standard: For medium and complex work. Maestro runs Design, Plan, Execute, and Complete phases with explicit approval gates, phased execution, and final review blocking on unresolved Critical or Major findings.
- docs/overview.md for the project model and generated structure
- docs/architecture.md for orchestration internals and architecture layout
- docs/usage.md for development workflow, settings, and command surfaces
- docs/flow.md for the orchestration workflow steps and hard gates
- docs/cicd.md for CI/CD pipeline workflows, release process, and Mermaid diagrams
- docs/runtime-gemini.md for Gemini runtime specifics
- docs/runtime-claude.md for Claude runtime specifics
- docs/runtime-codex.md for Codex runtime specifics
Apache-2.0