Skip to main content
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:
You get a table of known agents with status:

​
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.

​
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.

​
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.

​
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.

​
Next

Run your first task.