> ## Documentation Index
> Fetch the complete documentation index at: https://getpullrequest.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect a coding agent

> Install an ACP coding agent on the paired machine and verify it with gpr discover.

GPR does not host model APIs for your coding agent. It launches an agent process on your machine over **ACP** (Agent Client Protocol) stdio.

## Check what the daemon can see

On the paired machine:

```bash theme={null}
gpr discover
```

You get a table of known agents with status:

| Status          | Meaning                                                  |
| --------------- | -------------------------------------------------------- |
| `ready`         | CLI present and any required ACP adapter is available    |
| `needs adapter` | Agent CLI found; ACP bridge binary missing next to `gpr` |
| `not installed` | Required CLI not on `PATH`                               |

## Pick an agent

Built-in catalog ids include `cursor`, `claude`, `codex`, `kiro`, `opencode`, `qwen`, `cline`, and `copilot`.

For a first setup, **Cursor** is usually the simplest: it speaks ACP via `cursor-agent acp` and needs no separate adapter binary.

### Cursor

1. Install Cursor / `cursor-agent` so `cursor-agent` is on your `PATH`.
2. Run `gpr discover` and confirm **Cursor** is `ready`.
3. In the app, select Cursor on the workspace.

Details: [Cursor](/docs/integrations/coding-agents/cursor).

### Claude Code

1. Install the `claude` CLI and authenticate it (`ANTHROPIC_API_KEY` or Claude login).
2. Place the `claude-code-acp` adapter binary next to `gpr` (same directory as the daemon binary, usually `~/.local/bin`).
3. Confirm with `gpr discover`.

Details: [Claude Code](/docs/integrations/coding-agents/claude-code).

### Codex

1. Install the `codex` CLI and authenticate (`codex login` or `OPENAI_API_KEY`).
2. Place the `codex-acp` adapter binary next to `gpr`.
3. Confirm with `gpr discover`.

Details: [Codex](/docs/integrations/coding-agents/codex).

## Select the agent in the app

Open the workspace settings in the mobile app and choose the agent (and model if offered). The workspace stores the selected agent id and default model (default `auto`).

## Custom launch config

You do not need `~/.gpr/agents.json` for catalog agents that `gpr discover` marks `ready`.

Write that file when the agent must see env the background daemon does not inherit from your shell, or when you want a non-catalog ACP command. Details: [agents.json](/docs/reference/agents-json).

## Next

[Run your first task](/docs/get-started/run-your-first-task).