Claude, Codex, and Antigravity
Working with each of the three agent providers as panes on the canvas.
Agent Grid drives three agent CLIs as first-class pane types — claude, codex, and agy (Antigravity). Each spawns into its own PTY pane on the canvas; you talk to it like a terminal, and the orchestrator MCP plumbing on top is identical across all three.
The three provider panes
| Pane | Shortcut | CLI | Notes |
|---|---|---|---|
| Claude Code | Cmd1Ctrl1 | claude | Master-capable by default. Carries a sessionId so you can resume it from the spawn menu. |
| Codex | Cmd2Ctrl2 | codex | OpenAI's coding agent. Spawns the same way as Claude. |
| Antigravity | Cmd3Ctrl3 | agy | Google's agent CLI. |
Every provider pane is rendered through the same terminal pane component — a real node-pty PTY rendered with xterm.js. Shortcuts, ANSI colours, and chord behaviour are identical across the three. See Terminals for the chord details.
Sessions are recoverable on the Claude side. The spawn menu's Sessions → Resume Claude entry lists every Claude session under the active space's project folder so you can re-attach to one without re-typing a prompt.
Install and auth prerequisites
You install the agent CLIs the same way you would in any terminal — Agent Grid does not ship them. The "CLI not installed" alert in the spawn menu tells you exactly what to do.
Claude Code (claude)
Install per Anthropic's instructions, then run claude once in a terminal and authenticate against the Claude account you want Agent Grid panes to use. After that, spawning a Claude pane just works — Agent Grid picks up the same auth from your shell environment.
Codex (codex)
npm install -g @openai/codexAuthenticate codex in a regular terminal first (it walks you through the OAuth flow). Once that's done, Cmd2Ctrl2 opens a Codex pane.
Antigravity (agy)
Install from antigravity.google and run the CLI's first-launch login flow in a regular terminal. Then Cmd3Ctrl3 opens an Antigravity pane.
The "CLI not installed" alert that fires when you spawn a missing provider links to these exact install steps. If you see it, install the CLI in your normal shell first, restart the spawn, and Agent Grid will pick up the new binary on the next attempt.
For a deeper walkthrough of the per-platform install + first-launch flow, see Getting Started → CLI prerequisites.
What's actually running
Each provider pane is just a PTY running the underlying CLI in your shell, with your environment, your auth, and your project folder set as the working directory. Anything you can type into the CLI in a regular terminal works inside the pane — including --resume, --continue, and any provider-specific flags.
The orchestrator MCP layer is wired on top transparently: the master's MCP config is materialised on launch, and the Claude CLI is spawned with --mcp-config <path> so the worker, terminal, browser, and canvas tools are available without you configuring anything per-project.
Which provider for which job
Pick the provider that owns the task:
- Long orchestration sessions, fan-out review loops, mobile pairing, voice mode. Use Claude — the worker MCP surface and the voice overlay are wired to Claude panes specifically.
- Drop-in code generation against an OpenAI account. Use Codex.
- Drop-in code generation against a Google / Antigravity account. Use Antigravity.
You can run all three at once on the same canvas, each on its own pane, against the same project folder. Switching between them is the same as switching between any two panes — click, type.
Related
- Terminals — how the PTY pane behaves, shortcuts, chord translation.
- Orchestrating agents — driving Claude as a master with workers below it.
- Voice mode — the call overlay attaches to Claude panes.