Is Grok Build supported too?

Yes. concord setup also registers Grok Build, and any other MCP-capable agent can use the five tools.

Gemini CLI

Run Gemini CLI alongside Claude Code and Codex

Add Gemini CLI to a repo where Claude Code or Codex is already working, with shared claims, messages and task memory across all three.

The problem

Each vendor's agent is good at different things, but mixing them means three agents with three private views of the same codebase.

With Concord

01
Register Gemini
concord setup writes the MCP entry to .gemini/settings.json and installs Gemini's Concord extension, next to the Claude Code and Codex config.
02
Share the workspace
All three agents read and write the same .concord/ state, so a claim from Gemini is visible to Claude Code and Codex.
03
Route work by strength
Assign tasks to whichever agent suits them with transfer_work. The receiving agent accepts explicitly, so ownership is never implied.

Result

Adding a third vendor's agent adds a lane, not a third private context.

Is Grok Build supported too?: Yes. concord setup also registers Grok Build, and any other MCP-capable agent can use the five tools.