We launched Conductor final yr to carry spec-driven improvement on to your terminal. By shifting mission consciousness out of ephemeral chat logs and into persistent, version-controlled markdown recordsdata, Conductor has helped builders globally plan their architectures earlier than they construct.
In the present day, we’re excited to announce the following section of this journey: Conductor is evolving from a Gemini CLI extension into the Conductor Plugin. Plugins can embody abilities, guidelines, MCP servers, and hooks in a single package deal. Transitioning Conductor right into a plugin creates a extra fluid, conversational expertise with out sacrificing the procedural rigor of Spec-Pushed Growth (SDD). This additionally means Conductor is appropriate with instruments similar to Antigravity CLI.
Driving SDD by way of a pure dialog
By transitioning Conductor to a plugin, we’re eradicating the friction of strict command sequences. Conductor will now have interaction with you conversationally, dynamically producing context, specs, and plans organically as you talk about your characteristic necessities. You continue to get the advantages of persistent Markdown artifacts—your spec.md and plan.md aren’t going anyplace—however the course of of making and iterating on them is now so simple as chatting along with your AI assistant. It intelligently is aware of when to replace your context or verify off a accomplished activity in your plan, letting you concentrate on the structure whereas the AI manages the mission state within the background.
Conductor for Antigravity CLI and past
A good thing about transitioning Conductor to a plugin is that it breaks the workflow out to assist a number of instruments. Till now, Conductor has been completely tied to the Gemini CLI as an extension. By changing into a plugin, Conductor is now a transportable, ecosystem-wide functionality.
No matter which device you select, your AI agent will perceive the foundational paperwork about your mission’s structure, tips, and objectives. Your shared configuration and ongoing improvement tracks will persist seamlessly, that means an AI-assisted workflow began in a single device may be continued in one other with out dropping a single beat of context.
What this implies in your crew
- Backwards compatibility: The brand new Conductor Plugin works properly with outdated Conductor instructions and present plans and specs explicitly.
- Pure interplay: Spend much less time memorizing instructions and extra time discussing your implementation technique.
- Portability: Use Conductor within the device that matches your present activity, whether or not that’s Antigravity CLI, Claude, or different instruments.
- Preserved context: Keep the core promise of spec-driven improvement. Your repository stays the one supply of reality, however the way you work together with that reality is now much more intuitive.
- Improved activity completion: The Conductor Plugin achieved the next success price throughout essentially the most complicated subset of TerminalBench duties in comparison with a consumer not utilizing SDD.
Learn how to get began
Conductor’s mission has at all times been to assist make AI improvement secure, predictable, and architecturally sound. By evolving right into a conversational plugin, we’re making that energy extra accessible and adaptable to your distinctive workflow. We will’t wait to see what you construct subsequent.
Wish to study extra? Take a look at-drive the Conductor Plugin’s options in our hands-on Codelab.
Able to construct? Set up the plugin and begin utilizing the Conductor Plugin as we speak here, or run the next command to combine it with Antigravity CLI:
agy plugins install https://github.com/gemini-cli-extensions/conductor