maestro-frontier
Maestro Frontier local multi-CLI fusion engine - compose or choose a read-only model panel, inspect the catalog, arm, disarm, or run it
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- maestro-frontier
- license
- MIT
- description
- Maestro Frontier local multi-CLI fusion engine - compose or choose a read-only model panel, inspect the catalog, arm, disarm, or run it
03 SKILL.md 正文
Drive the Maestro Frontier engine: a local multi-CLI fusion engine where a
parallel panel feeds a judge and grounded synthesis. When a user asks to
compose or choose a model panel, route the request to frontier compose after
consulting frontier catalog; never guess a model or preset ID.
When the trusted Maestro Codex plugin hook is installed, arming a non-off
mode makes normal later Codex prompts auto-run through Frontier. run remains
an advanced, manual one-off. Do not edit Frontier state files by hand.
Command launcher
Use maestro when it is on PATH. If it is not, and this skill is loaded from
the Maestro Codex plugin, locate the plugin root by walking up from this
SKILL.md until .codex-plugin/plugin.json is present, then run:
node "<maestro-plugin-root>/bin/maestro.cjs" frontier ...
In the examples below, maestro frontier ... means either the bare command or
that plugin-root launcher.
Catalog and compose a panel
Use project scope from the repository root for state-changing commands:
maestro frontier catalog
maestro frontier catalog --json
maestro frontier compose --models <model>,<model> --dry-run --scope codex-project
maestro frontier compose --models <model>,<model> --judge <model> --synth <model> --effort <level> --scope codex-project
maestro frontier compose --models <model>,<model> --save <name> --scope codex-project
maestro frontier effort <auto|low|medium|high|xhigh|max|ultra> --scope codex-project
frontier catalog is the source of truth for models, presets, aliases,
readiness, and required configuration. compose accepts one to eight
comma-separated models. Judge and synth default to the first panel model.
--dry-run changes nothing; a non-dry run saves and arms the resolved custom
fusion panel. --effort persists one validated level across panel, judge, and
synth stages for selected effort-aware Claude and Codex models. effort auto
returns the armed panel to provider defaults.
Modes, inspection, and saved presets
maestro frontier mode off --scope codex-project
maestro frontier mode single --model <model> --scope codex-project
maestro frontier mode fusion --preset <preset> --scope codex-project
maestro frontier mode fusion --preset custom --models <model>,<model> --scope codex-project
maestro frontier status --scope codex-project
maestro frontier roster
maestro frontier preset save <name> --models <model>,<model> --judge <model> --synth <model> --scope codex-project
maestro frontier preset list --scope codex-project
maestro frontier preset delete <name> --scope codex-project
Use catalog before selecting any model or preset. roster reports only
readiness and configuration names, never secret or configured model values.
Current models, overrides, and release gate
opus pins Claude Opus 5.5 (claude-opus-5-5), fable pins Fable 5.1
(claude-fable-5-1), sonnet-5 keeps Sonnet 5 (claude-sonnet-5), and
haiku adds Haiku 4.5 (claude-haiku-4-5-20251001). Claude Code v2.1.280+
is required for Opus 5.5; v2.1.257+ is required for Fable 5.1.
Opus, Fable, and Sonnet support low, medium, high, xhigh, and max;
Haiku has no effort flag.
Codex selectors include astra (gpt-6-astra), sol (gpt-6-sol),
terra (gpt-5.6-terra), and luna (gpt-6-luna), plus auto-review and
the retained GPT-5.5, GPT-5.4, GPT-5.4 Mini, and GPT-5.3 Codex Spark selectors.
GPT-6 models support low, medium, high, xhigh, and max in Maestro’s
UI, without none or ultra. Earlier explicit selectors and third-party
adapters remain available.
Use frontier catalog for exact aliases and supported effort levels.
MAESTRO_FRONTIER_MODEL_TERRA, MAESTRO_FRONTIER_MODEL_LUNA, and
MAESTRO_FRONTIER_MODEL_SOL remain optional model-ID overrides. Codex Desktop
/ IDE sessions read those overrides from ~/.codex/.env; restart the app and
open a new thread after changing it.
Before releasing Codex catalog changes, probe every first-party Codex selector:
node frontier/smoke.cjs
This explicit release gate invokes those selectors through the normal read-only dispatch path.
Normal and debug use
After mode is non-off, use ordinary Codex prompts; the trusted hook supplies
the Frontier result. Turn it off or run one manual prompt with:
maestro frontier mode off --scope codex-project
maestro frontier run "<prompt>" --scope codex-project
All panel, judge, and synthesizer subprocesses are one-shot and read-only:
they return text only and never edit the workspace, commit, or run autonomous
loops. On ERROR [<reason>]: <detail>, relay the reason.
Indicator instruction
<!-- INDICATOR INSTRUCTION - apply every turn while this skill is active -->
Before composing your first reply each turn, run:
maestro frontier status --scope codex-project
Parse the returned JSON mode field:
- If
modeis notoff, make the first line of your reply exactly:Maestro Frontier ON (<label>)where<label>issingle - <model>orfusion - <preset>; for a custom preset usefusion - custom (<model1>, <model2>, ...). - If
modeisoff, output no indicator line.
<!-- END INDICATOR INSTRUCTION -->
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.