codex-maestro

Orchestrate software changes with a Sol root and Luna worker agents in Codex.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/akoita/agent-toolkit --skill codex-maestro-akoita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-maestro
Source: https://github.com/akoita/agent-toolkit/tree/main/plugins/portable/codex-maestro/skills/codex-maestro
Command: npx skills add https://github.com/akoita/agent-toolkit --skill codex-maestro-akoita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Coordinating non-trivial software changes across multiple AI agents risks unverified model routing, unbounded delegation, and unreviewed worker output. This Skill enforces a verified orchestration workflow where a root agent plans and reviews while bounded workers implement and explore. ## Core Features & Use Cases - Verified routing: Fail-closed preflight checks confirm the root runs gpt-5.6-sol at medium effort and workers run gpt-5.6-luna at max effort by parsing persisted rollout metadata. - Bounded delegation: Implementation and exploration workers receive explicit file ownership, constraints, and verification commands, with conflict detection for overlapping edits. - Root-owned review and publication: The root independently inspects diffs, runs tests, and is the only agent allowed to commit, push, or publish. - Use Case: When implementing a multi-file feature in Codex, use this Skill to verify routing, delegate bounded code changes to a Luna worker, and review the actual workspace diff before committing. ## Quick Start Ask Codex to use the codex-maestro skill to plan and implement your feature, then run the routing preflight before delegating any work.

Frequently Asked Questions about codex-maestro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate coding tasks across multiple Codex agents?▼

Use a root maestro agent to analyze, plan, and review while delegating bounded work items to implementation and exploration workers. Each assignment must state the goal, owned files, constraints, and exact verification commands.

How do I verify which model a Codex agent is actually running?▼

Run the check_routing.py script with --enforce to validate the root's persisted rollout metadata and installed agent definitions. For a spawned worker, pass its exact rollout file with --worker-rollout and --role to confirm model and effort.

What models and effort levels does Codex Maestro require?▼

The only supported route is a gpt-5.6-sol root at medium effort with gpt-5.6-luna workers at max effort. Any other root model, worker model, or reasoning effort fails the routing check and requires an explicit user override.

Can Codex Maestro workers commit or push changes?▼

No. Workers are forbidden from committing, pushing, opening pull requests, deploying, or performing any external side effects. Only the root maestro may publish changes, and only when the user has authorized those actions.

When should I not use multi-agent orchestration for coding?▼

Skip orchestration for trivial edits and pure analysis or review tasks, where delegation overhead outweighs the benefit. The workflow targets non-trivial changes like features, refactors, and multi-step debugging.