Continue the conversation — chat opens pre-seeded with the current signal, caps, and movement.
Google-backed workflow extension for Gemini CLI adding structured Spec-to-Plan-to-Implement development using persistent Markdown context files. Target user: Gemini CLI users who want structured AI workflows (specs, plans, implementations, automated reviews) rather than free-form prompting. Strongest fit for individual developers and small teams already invested in the Gemini ecosystem.
Differentiator: Universal File Resolution Protocol and tracks abstraction for persistent context across sessions; Automated Review feature that validates code quality, runs the test suite, and scans for critical vulnerabilities; git-aware smart-revert and Git-notes verification trail.
Strategic context (May 2026): the underlying Gemini CLI is being transitioned to Antigravity CLI (deprecation June 18, 2026). Extensions migrate as 'Antigravity plugins,' but Conductor has no published Conductor-specific migration path, and Google appears to be reworking its spec/plan capability toward native Antigravity/Gemini-CLI planning building blocks.
Adoption & Proof Points
- **GitHub:** 3.6k stars, ~280 forks, 61 open issues, 13 open PRs
- **Google promotional channels:** featured at Google Next '26 Codelabs (Plan and Build Apps with Gemini CLI Conductor); Developer Blog coverage (intro + Automated Reviews update)
- **Substrate transition:** Gemini CLI → Antigravity CLI announced at I/O 2026 (May 19), deprecation June 18, 2026; extensions become Antigravity plugins but no Conductor-specific continuity commitment
- **No named enterprise customers** for Conductor specifically
- **Cadence stalled:** no tagged release since v0.4.1 (March 11, 2026) — 78 days at the time of this evaluation, approaching the 90-day stalled-development threshold
Risks & Limitations
- **Substrate deprecation (NEW, major):** Gemini CLI stops working June 18, 2026 for free/Pro/Ultra users; extensions migrate as Antigravity plugins but Google has made no Conductor-specific migration commitment. gemini-cli issues #16749 (rework onto native planning) and #22709 (clean up Conductor extension) suggest the function may be absorbed natively rather than the standalone extension sustained. Drove viability 11→10.
- **Stalled-development watch:** 78 days since v0.4.1; the 90-day threshold (~June 9) would trigger the stalled-development cap (all dims ≤12).
- **`reliability-complaints` cap active:** plan-mode prompt loop (Issue #153) and workflow conflict with Gemini CLI built-ins (Issue #18305) remain open and unfixed.
- **`no-codebase-indexing` cap:** Conductor explicitly avoids codebase indexing; context is managed-Markdown plus the model window, not a semantic index.
- **`no-enterprise-features` cap:** all dimensions capped at 14.
- **Naming collision:** Melty Labs Conductor (macOS multi-agent app), Orkes/Netflix Conductor, and codeconductor.ai all surface in analyst pieces — discovery/positioning risk.
- **Token cost:** context-driven approach increases token consumption on larger projects (acknowledged in docs).
Capabilities & Integration
**Autonomy (12, Agentic floor, capped by reliability-complaints):** Spec→Plan→Implement protocol, Automated Review (code review, test-suite validation, basic security scan), git-aware smart-revert. Inherits Gemini CLI autonomous tool use. Cap holds at 12 because Issue #153 (plan-mode loop) and Issue #18305 (workflow conflict) are unfixed.
**Integration (9, Basic): ** git operations via underlying Gemini CLI; release-please CI awareness; smart-revert; Git-notes verification trail. No native Linear/Jira/Slack; no Conductor-specific PR creation/review beyond Gemini CLI / run-gemini-cli defaults.
**Context (11, Project-Aware ceiling, capped by no-codebase-indexing):** persistent Markdown context files via Universal File Resolution Protocol and tracks abstraction; large model context window. No codebase indexing/embeddings/RAG.
**Viability (10, Funded/Growing lower end):** Google-backed, but standalone continuity uncertain under the June 18 2026 Gemini CLI → Antigravity CLI transition with no Conductor-specific migration path, plus a stalled 78-day release gap.
**Interface (7, Single-Mode ceiling):** Conductor commands (`/conductor:setup`, `/conductor:newTrack`, `/conductor:implement`, `/conductor:review`) execute exclusively inside the Gemini CLI terminal. No IDE plugin, GUI, API, or headless mode for Conductor itself. The Gemini CLI VS Code Companion does not expose Conductor commands.