Gemini

Google Gemini CLI support for teams already using Gemini-based coding workflows.

Agent guide

Gemini gives teams another first-class routing option when selected repositories already lean on Google-based coding workflows, model families, or internal standards.

Binary: geminiAliases: gm, gemini-cliBest for vendor-diverse fleets

Primary binary

gemini

Known aliases

gm, gemini-cli, google-gemini

Good fit

Multi-agent fleet diversity, CLI parity, and model portfolio flexibility.

​

Set up Gemini in Conductor

1. Install Gemini CLI

   npm install -g @google/gemini-cli
   
2. Complete authentication

   Finish the Gemini CLI sign-in flow so the binary works in the same environment that will launch Conductor.

3. Launch Conductor

   npx --yes --registry=https://registry.npmjs.org conductor-oss@latest
   

   Add or update the workspace and choose Gemini as the project default where it belongs.

4. Set the repo default

   projects:
     my-app:
       agent: gemini
   

​

Model selection in Conductor

Gemini model availability comes from your Gemini CLI environment and Google account permissions.

• leave agentConfig.model unset when Gemini should keep using its own current default
• add a pinned override only when a repository needs a fixed Gemini target
• if your team already manages Gemini profiles outside Conductor, keep that source of truth there and use Conductor for routing

​

Why teams pick Gemini

• keeps the fleet from collapsing into one vendor
• good fit for teams already using Gemini tools elsewhere
• clean fallback or alternate default for specific repositories