AgentGridAgentGrid Docs
Getting Started

Coding harness setup

Install, detect, and sign in to the AI coding harnesses AgentGrid can run.

AgentGrid runs the coding harnesses installed on your computer. You only need one to get started, and you can add more whenever you want a mixed-agent team.

Install and sign in inside AgentGrid

On first launch, the Connect a coding CLI screen checks which harnesses are installed. For a missing harness, choose Install: AgentGrid runs the provider's official installer for you, with no Node.js or npm needed. Once a harness shows Ready, its first use signs you in. Cursor and Pi have no one-click install on Windows; use their Docs link instead.

Install and sign-in actions are available later from Settings -> Agents, Settings -> Accounts and the usage popover. Signing in to Claude opens your browser, with no terminal step. In an agent's chat, type /login to sign in or switch that agent to another account, or /logout to sign it out on this computer, for harnesses that support it.

In Settings -> Agents, installed harnesses appear at the top of the list. The spawn menu lists only the agents AgentGrid has confirmed are installed and enabled; it shows Checking agents… while it looks, and asks you to reopen it if the check fails. AgentGrid only polls usage for CLIs that are installed.

Claude Code, Codex, and Antigravity can each have more than one signed-in account, so a second subscription or a Gemini API key can run alongside your main login. Adding a second account needs AgentGrid Pro; accounts you already added keep working on Free. See Multiple accounts per harness to add one and pick which pane runs as which account.

You do not need every harness. Install and authenticate only the ones you plan to run. Terminal, source control, browser, note, and media panes have no harness prerequisite.

Supported harnesses

HarnessCLI AgentGrid detectsCan be a team leadCan run as a worker
Claude CodeclaudeYesYes
CodexcodexYesYes
OpenCodeopencodeYesYes
AntigravityagyYesYes
Cursorcursor-agentYesYes
DevindevinYesYes
GrokgrokYesYes
HermeshermesYesYes
KimikimiYesYes
PipiYesYes
Muse CodemuseNoNo

"Can be a team lead" means the harness can open as a team lead pane with AgentGrid's worker, terminal, browser, and canvas tools, so it can start and steer workers. Muse Code runs in its own pane on the canvas, but it can't start workers or be started as one yet.

If you've turned on Claude in Chrome by default in Claude Code, Claude panes and workers in AgentGrid can use it too. Claude in Chrome pairs with one Claude account: if a pane on another account finds no browser, it names the account that last saw your browser, with Switch to move the pane to that account.

Keeping harnesses up to date

AgentGrid updates harness CLIs automatically while they're idle: a harness updates only when none of its agents are running. Starting an agent on that harness during the short install is refused with "is updating; try again in a moment". A CLI installed with npm is updated where it's installed, with that install's own npm. In Settings -> Agents, each harness shows its version and when it was last checked or updated; when an update is available it also shows Update now and an Auto-update switch. Devin manages its own updates, so AgentGrid leaves it alone, and Hermes has no Auto-update switch: it updates only when you choose Update now.

Verify a manual installation

The in-app installer is the easiest route. If you install a CLI yourself, verify the exact binary name from your normal shell:

claude --version
codex --version
opencode --version
cursor-agent --version

Use the matching command from the table for the other harnesses. AgentGrid also looks in the usual per-user install folders, such as ~/.local/bin, ~/.opencode/bin and ~/.cargo/bin (and %APPDATA%\npm on Windows), even when they aren't on your PATH. If AgentGrid still doesn't find a CLI you installed elsewhere, restart AgentGrid so it picks up your PATH changes. During setup, Setup AI adds a missing folder to your PATH itself and checks again without a restart.

If AgentGrid still says a CLI is missing

  • Confirm the exact binary is available to the user account that launched AgentGrid.
  • Restart AgentGrid after changing your shell profile or PATH.
  • On macOS, remember that an app opened from the Dock can see a different PATH from a shell.
  • On Linux, the AppImage inherits the environment that launched it; the .deb package can be simpler when you depend on user-level shell configuration.
  • On Windows, if a CLI install is broken, AgentGrid's error names the exact missing file. Reinstall that CLI.
  • Open Settings -> Agents and retry the install or login action for that harness.

Authentication belongs to the underlying provider account. AgentGrid reuses the credentials maintained by that harness rather than asking you to paste them into each pane.

Next step

With one harness ready, continue to the Quickstart.

On this page

Ask AI

Ask a question about AgentGrid. Answers come from these docs, with links to the pages they use.

AI answers can be wrong. Check the linked pages.