Ai Coding 3 min read

Portable Conductor Plugin Brings Spec-Driven Dev to Claude

Google has decoupled Conductor from the Gemini CLI, releasing a portable plugin that brings conversational Spec-Driven Development to Antigravity and Claude.

On July 16, 2026, Google Developers transitioned Conductor from a dedicated Gemini CLI extension into a portable plugin architecture. The official release expands Spec-Driven Development (SDD) across external ecosystems, most notably adding native integration for the Antigravity CLI and Anthropic’s Claude model family. The architectural shift signals a broader move by Google toward model-agnostic orchestration for development workflows.

Portable Plugin Architecture

The primary technical change decouples Conductor’s core logic from Google’s proprietary toolchain. Conductor now functions as a modular engine designed to be injected into third-party command-line environments.

The initial rollout centers on Antigravity, a high-performance developer toolchain. Developers can now manage complex project specifications and trigger code generation directly through the Antigravity interface while routing the underlying reasoning tasks through Conductor.

By unbundling the orchestration layer from the model execution, Google allows developers to automate workflows using the models best suited for specific engineering tasks. The official inclusion of Claude indicates a pragmatic acknowledgment that multi-model environments are the standard for modern software engineering.

Conversational Spec-Driven Development

Traditional scaffolding tools rely on rigid command sequences for state changes. Conductor replaces this paradigm with a conversational interface that dynamically manages project state.

As you chat with the CLI, Conductor maintains a hidden specification file, or “Spec”, updating implementation details and requirements in real-time. When switching between tasks, the engine injects this current Spec directly into the model’s context window. This ensures the model remains grounded in the project’s specific technical constraints without requiring manual prompt engineering.

The Antigravity integration builds upon this with automated validation loops. The CLI evaluates all generated code against the active Spec before presenting it to the user, reducing the risk of drift in long-running agent interactions. This approach shifts the developer’s role from managing individual syntax tasks to governing the overarching system state, similar to how developers evaluate and test AI agents in production.

Capability Shift

The transition reshapes the constraints of the Conductor environment:

FeatureLegacy ConductorPortable Conductor Plugin
Core ArchitectureGemini CLI ExtensionModular CLI Plugin
Supported ModelsGeminiGemini, Claude
Toolchain IntegrationGoogle-specificAntigravity, External CLI tools
State ManagementCommand-driven scaffoldingConversational real-time spec updates

Installation and Availability

The portable plugin format is available immediately via the Google Developers GitHub repository. Developers operating within the Antigravity environment can install the update using the standard antigravity plugin add conductor command.

If you manage complex codebases using Spec-Driven Development, the decoupling of Conductor allows you to centralize your architectural requirements in a persistent state file while leveraging Claude for execution. You can now rely on the CLI to handle context injection and validation automatically.

Get Insanely Good at AI

Get Insanely Good at AI

The book for developers who want to understand how AI actually works. LLMs, prompt engineering, RAG, AI agents, and production systems.

Keep Reading