Skip to main content
GPR’s daemon is an ACP host. Any catalog agent that speaks ACP over stdio can run tasks and chats.

​
Built-in catalog

​
Discovery

Ready means:
  1. Every binary in Requires is on PATH.
  2. If an adapter is required, that binary exists beside gpr.

​
Selecting an agent

Set the agent on the workspace in the app. Tasks use that workspace’s agent when claimed.

​
Protocol path

The backend does not embed the agent. It relays frames and stores task/session metadata.

​
Adding new agents later

New catalog entries ship with daemon releases. Prefer agents that already appear in gpr discover. When you need a custom ACP binary, extra env (API keys, proxy URLs), or an agent id that is not in the catalog, write agents.json. Names in that file are advertised to the app on connect. A catalog id you redefine fully replaces the built-in launch spec.