Everything between “here’s the plan” and “it’s merged”
Maestro Studio runs the orchestration; the Maestro Client runs the work. Together they cover planning, decomposition, dispatch, execution, review and reporting.
The web orchestration plane
Laravel + Livewire web app: workspaces, projects, AI planning, kanban, knowledge browser, skill management, invites and live dashboards over WebSockets.
- AI plan chat & plan editor
- Kanban / list / timeline task views
- Knowledge browser with vector search
- Real-time run & dashboard streams
The developer CLI daemon
A single Rust process per machine that auto-detects projects, holds parallel WebSocket connections, and drives your AI provider through a state machine.
- Auto-detect via git remote
- Multi-project, multi-identity
- Provider adapters + manual mode
- ratatui TUI with operator steering
An open WS contract
JSON-RPC 2.0 over Laravel Reverb (Pusher v7), one private channel per project. Documented channel events, error codes and reconnect semantics — not a black box.
- JSON-RPC 2.0 envelope
- JWT per-channel scope
- 30s heartbeat, 30s backoff cap
- Documented channel events & error codes
What you actually get
AI planning & re-planning
A planning agent turns a goal into phases and tasks. Scope changes, agent subtask directives and reviewer verdicts re-plan automatically.
Skill system
Workspace skill slugs with a normalized 1–5 proficiency scale (and percent buckets). Tasks declare required proficiency; dispatch matches it.
Auto & manual dispatch
Let the dispatcher route work, or assign on the kanban board. Leads can delegate subtask packets straight to workers.
Team spawning
maestro team --dev 2 --review 1 --test 1 spawns detached workers on a shared channel under one lead.
Deterministic review loop
AI only renders a verdict; the server merges on APPROVED or re-dispatches the developer on the same branch on REJECTED, capped at 3 cycles.
Epic & release flow
Each plan gets its own pinned epic branch; tasks merge into it, then the whole plan is released to the base and its branches torn down.
Pause & recovery
Pause a plan, ride out provider rate limits, and auto-reclaim runs orphaned by dead sessions — orchestration that survives interruption.
Provider sandbox
Agents refuse unsafe directories and run confined to the task worktree, with a model sized to the run’s purpose.
Reporting
Token, duration and estimate-vs-actual tracking per run feeds daily reports, performance analysis and improvement suggestions.
See the full architecture
The docs walk through every component, endpoint and flow.