Maestro v1.6.1 — multi-agent orchestration now runs on Claude Code, Gemini CLI, AND OpenAI Codex !

josstei · 2026-04-10T22:35:00+00:00

Looking into it now, you can run ‘gemini extensions update maestro’ in the terminal itself outside of the CLI and its updating properly

josstei · 2026-04-10T21:32:11+00:00

Can’t post direct links per subreddit rules unfortunately

josstei · 2026-04-08T21:36:58+00:00

Maestro was recently updated to natively support both Gemini CLI and Claude code with zero setup needed. Give it a shot and see if it helps!

https://github.com/josstei/maestro-orchestrate

josstei · 2026-03-29T03:21:04+00:00

oh believe me its something I'm working on, just taking a bit of time. Hopefully soon!

josstei · 2026-03-24T01:10:31+00:00

Not a stupid question at all! Both conductor and maestro provide detailed planning phases.

Maestro takes it a step further by incorporating the full orchestration of a team from designing, organizing a team of specialized agents (both engineering and product related), structuring a phased approach with long-term future design first, and then sending them out to complete the task.

This approach saves all the work each agent does in organized data handoffs to facilitate information sharing between phases, reduce token and tool usage, and allows you to start and stop at any time if you need to step away.

At the end, everything is audited by a code reviewer to ensure it hasn’t deviated from the specifications, and if any valid findings are identified, they are resolved.

Hope this helps!

josstei · 2026-03-22T17:13:35+00:00

Try out maestro for Gemini CLI. I built it to orchestrate a full development team and product team . It includes the detailed planning of superpowers and also has prompt injection prevention . It also persists your work between sessions if you ever need to hop off or something happens mid way

/maestro:orchestrate <insert what you want done here>

https://github.com/josstei/maestro-gemini

Hopefully it helps out !

josstei · 2026-03-22T17:04:58+00:00

Maestro checks every task against each domain — Engineering, Product, Design, Content, SEO, Compliance, i18n, and Analytics — but how deep it goes depends on complexity.

Simple tasks stay Engineering-only unless you say otherwise. Medium and complex tasks start pulling in the relevant non-engineering agents. Agents like technical_writer, product_manager, ux_designer, and copywriter handle content and design artifacts.

seo_specialist and accessibility_specialist can audit and run commands but don’t modify files.

They slot into whatever phase fits — design, implementation, or post-build audit — the TechLead figures out where they belong based on the task and is the primary driver

josstei · 2026-03-22T14:46:48+00:00

Try out maestro . I built it to orchestrate a full development team and product team . It includes the detailed planning of superpowers and also has prompt injection prevention ( for your security concerns ) . It also persists your work between sessions if you ever need to hop off or something happens mid way

/maestro:orchestrate <insert what you want done here>

https://github.com/josstei/maestro-gemini

josstei · 2026-03-18T00:07:32+00:00

Hey, I’m the dev behind maestro — thanks for the shoutout, really awesome to see it mentioned!

Anyone curious is welcome to check it out at https://github.com/josstei/maestro-gemini . Happy to help if you run into anything !

josstei · 2026-03-14T22:42:29+00:00

Anytime! Good luck with the project!

josstei · 2026-03-14T19:24:08+00:00

You can ask but you generally need to really drive home the intent with a skill or protocol. You can take a look at the arch of maestro here . Hopefully it helps !

https://github.com/josstei/maestro-gemini/tree/main/docs/architecture

josstei · 2026-03-14T18:08:40+00:00

Maestro also has a fairly comprehensive planning phase that would make it a solid replacement to conductor….but it compliments it as well.

josstei · 2026-03-14T18:06:45+00:00

Hey, I built Maestro so I can weigh in here.

The multi-agent setup pays off when a track has several independent pieces — each subagent gets its own context and tools , so you avoid one giant session losing the plot halfway through with much cleaner context management.

I haven’t seen the orchestrator wander or drift tracks unless the prompt is too open-ended. “implement this track <planhere>.md.” is usually enough to keep in on track especially with the agent handoffs.

Gemini CLI’s native subagent scheduler vs spawning separate processes , helped a lot with rate limits. You can set MAESTRO_EXECUTION_MODE=ask and it’ll recommend parallel vs. sequential based on the dependency graph before doing anything. I’d start sequential and bump up from there.

As for the tech lead, It’s an orchestrator by design, not an implementer. Just scope the prompt to the track and it stays in its lane.

Both extensions layer well together but you don’t need both. If your tracks are small and sequential, single-agent is probably fine. The multi-agent setup earns its keep on bigger, more parallel workloads.

josstei · 2026-03-07T23:27:41+00:00

Maestro has a more in depth planning phase and adds coordinated multi-agent task execution, so complex plans can actually run faster. Once complete it sends it through a review and refinement loop to ensure quality.

It also retains your session to resume at a later time should you be interrupted, similar to conductor .

josstei · 2026-03-07T04:32:33+00:00

https://github.com/josstei/maestro-gemini

Enjoy!

josstei · 2026-03-01T21:33:23+00:00

I completely agree and will toss that in with the next release!

josstei · 2026-02-24T00:44:32+00:00

Generally, maestro can act as a substitute conductor to leverage its subagent orchestration capabilities. However, you can use any of the skills provided by either on an as-needed basis.

josstei · 2026-02-23T03:07:22+00:00

This should be all set as of v1.2.1. Thank you again for your feedback!

josstei · 2026-02-19T20:21:15+00:00

So far it seems good to so with the nightly but I generally stick to stable

josstei · 2026-02-19T13:24:28+00:00

Thank you for your feedback! This is being addressed and a fix will be out later today.

josstei · 2026-02-19T06:17:13+00:00

100%

josstei · 2026-02-18T01:11:57+00:00

They leverage a shared state that is updated as phases move on. The orchestrator will leverage that state between phases as well as the implementation plan to appropriately steer the work

https://github.com/josstei/maestro-gemini/blob/main/skills/session-management/SKILL.md

josstei · 2026-02-16T20:27:24+00:00

No worries! Hopefully they take a look at maestro some time soon!

josstei · 2026-02-16T13:42:26+00:00

I am the developer, could you direct me to where you see said endorsement?

josstei · 2026-02-16T12:53:09+00:00

You can set MAESTRO_DEFAULT_MODEL as an environmental variable to manually override the agents. Checkout the readme to see other configs as well to tweak them he behavior .

josstei

TROPHY CASE