Maestro v1.5.0 adds Claude Code support for multi-agent orchestration

What Maestro v1.5.0 delivers

Maestro is an open-source multi-agent orchestration platform that coordinates 22 specialized AI subagents through structured workflows including design dialogue, implementation planning, parallel execution, and quality gates. Originally a Gemini CLI extension, version 1.5.0 now runs on Claude Code as a native plugin.

Installation commands

For Gemini CLI:

gemini extensions install https://github.com/josstei/maestro-orchestrate

For Claude Code:

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

Key features in v1.5.0

• Claude Code support: The entire platform — all 22 agents, 12 commands, methodology skills, lifecycle hooks, MCP state management — now works as a Claude Code plugin. Agents appear with a maestro: prefix and all slash commands (/orchestrate, /review, /debug, /security-audit, etc.) work out of the box.
• Deeper design and planning: Design dialogue scales rigor by depth level. Standard mode adds inline rationale annotations on every key design decision. Deep mode adds per-decision alternatives, trade-off narration, and full requirement traceability with bidirectional linking. Design sections scale by task complexity — simple tasks get 3 concise sections, medium tasks get 5, complex tasks get all 7 with 200-300 words each. A formal revision protocol ensures revised sections are re-presented for approval inline, with conflict detection if later sections invalidate earlier decisions.
• 42-step orchestration backbone: Both runtimes now load the same numbered-step procedural sequence from a single shared reference file. Hard-gates enforce critical checkpoints — plan validation before presentation, per-phase state transitions, delegation-only remediation after code review. The orchestrate command was reduced from 347 inlined lines (Gemini) / 773 lines (Claude) down to thin runtime preambles.
• Agent capability enforcement: A new server-side validation rule catches plan misconfigurations where read-only agents get assigned to file-creating phases — before execution starts, not after it fails. Implementation planning now includes an agent-deliverable compatibility check as a hard-gate.
• Security hardening: Path containment validation on session state directories, symlink checks on hook state, fail-closed policy enforcement on shell commands, bounded stdin reads (1 MB cap), explicit file permissions, and filesystem path stripping from MCP error messages.
• Deferred resource loading: Templates and references are loaded at the step where they're consumed instead of all at once during classification, keeping the context window lean for relevant phases.

How Maestro works

You describe what you want to build. Maestro classifies task complexity (simple/medium/complex), asks structured design questions, proposes architectural approaches with trade-offs, generates an implementation plan with dependency graphs, then delegates to specialized agents — coder, tester, architect, security engineer, data engineer, etc. — with parallel execution for independent phases.

Simple tasks get an Express workflow (1-2 questions, brief, single agent, code review, done). Complex tasks get the full Standard workflow with a design document, implementation plan, execution mode selection, and quality gates.

The platform includes 22 agents across 8 domains: Engineering, Product, Design, Content, SEO, Compliance, Internationalization, Analytics. Each agent has least-privilege tool access enforced via frontmatter — read-only agents can't run shell commands, shell-only agents can't write files.