We launched Conductor final 12 months to convey spec-driven growth on to your terminal. By shifting undertaking consciousness out of ephemeral chat logs and into persistent, version-controlled markdown information, Conductor has helped builders globally plan their architectures earlier than they construct.
As we speak, we’re excited to announce the following part of this journey: Conductor is evolving from a Gemini CLI extension into the Conductor Plugin. Plugins can embody expertise, guidelines, MCP servers, and hooks in a single bundle. Transitioning Conductor right into a plugin creates a extra fluid, conversational expertise with out sacrificing the procedural rigor of Spec-Pushed Improvement (SDD). This additionally means Conductor is appropriate with instruments resembling 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 interact with you conversationally, dynamically producing context, specs, and plans organically as you focus on your characteristic necessities. You continue to get the advantages of persistent Markdown artifacts—your spec.md and plan.md aren’t going wherever—however the course of of making and iterating on them is now so simple as chatting together with your AI assistant. It intelligently is aware of when to replace your context or examine off a accomplished process in your plan, letting you deal with the structure whereas the AI manages the undertaking 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 solely 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 undertaking’s structure, pointers, and targets. Your shared configuration and ongoing growth tracks will persist seamlessly, which means an AI-assisted workflow began in a single device might be continued in one other with out shedding a single beat of context.
What this implies on your staff
- Backwards compatibility: The brand new Conductor Plugin works nicely with previous Conductor instructions and current 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 process, whether or not that’s Antigravity CLI, Claude, or different instruments.
- Preserved context: Keep the core promise of spec-driven growth. Your repository stays the only supply of fact, however the way you work together with that fact is now way more intuitive.
- Improved process completion: The Conductor Plugin achieved a better success fee throughout essentially the most advanced subset of TerminalBench duties in comparison with a consumer not utilizing SDD.
The way to get began
Conductor’s mission has at all times been to assist make AI growth 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 are able to’t wait to see what you construct subsequent.
Need to be taught 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 right here, or run the next command to combine it with Antigravity CLI:
agy plugins set up https://github.com/gemini-cli-extensions/conductor
