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, AgentGrid checks which harnesses are available. For a missing harness, choose Install; after installation, choose Sign in and complete the provider's login flow without leaving the app.
The same install and login actions are available later from Settings -> Agents and the usage popover. If you choose a harness whose CLI is missing, the spawn menu opens its install guidance. AgentGrid caches detection results and only polls usage for CLIs that are installed.
You do not need every harness. Install and authenticate only the ones you plan to run. Terminal, code editor, source control, browser, note, and media panes have no harness prerequisite.
Supported harnesses
| Harness | CLI AgentGrid detects | Can orchestrate | Can run as a worker |
|---|---|---|---|
| Claude Code | claude | Yes | Yes |
| Codex | codex | Yes | Yes |
| OpenCode | opencode | Yes | Yes |
| Antigravity | agy | No | Yes |
| Cursor | cursor-agent | Yes | Yes |
| Devin | devin | Yes | Yes |
| Grok | grok | Yes | Yes |
| Kimi | kimi | Yes | Yes |
| Pi | pi | No | Yes |
"Can orchestrate" means the harness can open as a master pane with AgentGrid's worker, terminal, browser, and canvas MCP tools. Every installed harness in the table can be selected for a worker.
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 --versionUse the matching command from the table for the other harnesses. Then restart AgentGrid so the desktop process picks up any PATH changes.
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
PATHfrom a shell. - On Linux, the AppImage inherits the environment that launched it; the
.debpackage can be simpler when you depend on user-level shell configuration. - 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.