Install an agent from the ACP registry
The ACP registry is a public list of coding agents that speak the Agent Client Protocol. Your organization can install any of them for its tasks. For what an agent is and how a task runs one, see How agents work.
Plan: your plan lists each registry agent on its own. The Registry tab shows the ones your plan includes; with none, there is no Registry tab, and opening it directly shows Not on your plan: "Your plan doesn't include registry agents." An installed agent your plan stops including no longer runs: its tasks fail with the reason. Its bound key account must also use a provider and authentication your plan includes. To get it, see Ask to change your plan.

Role: everyone can browse the registry and see what's installed. Installing, binding a key account and removing need the org admin role. Everyone else sees the note "Only admins can install registry agents." above the list. If the registry lists no agents at all, the tab reads No registry agents.
Install one
- Open Settings, then Agents under Customize.
- Select the Registry tab.
- Find the agent. Type its name in Name, or narrow the list with Distribution (All types, Binary, npm or Python) and Status (All statuses, Installed or Installable). On a phone, both filters sit in the Filters menu beside the search. Cards that can't be installed come last. When nothing matches, the page reads No matching agents; Clear filters resets the search and both filters.
- Read its card: its version, distribution, maintainer and license.
- Press Install. The button reads Installing… until it's done, then a note confirms it: "Installed", the agent's name, and "Pinned. Installs on the node when a task runs."
- Check the card. It now shows Installed · pinned v and the version. On the Custom agents tab, the agent is listed as Active.
Installing only pins the agent to the version shown. The agent downloads for each task that runs it, and never updates on its own. To move to a newer version, remove it (below) and install it again.
An installed agent belongs to your organization only. Other organizations don't see it.
Give it a key account
An agent that signs in with an API key uses one of your organization's API-key model accounts.
- Select the Custom agents tab.
- Select the agent's name to open its page.
- In API-key account, type to search, then pick the account. Each one shows its provider beside its name; accounts from the agent's own vendor come first, marked same vendor. Clear the field to unbind it: it then reads None.
- Press Save. A note names the change. On the list, hover the agent's name to see Key: and the account's name (Key account set if it isn't one you can see), or No key account; its ⋯ menu, and the page's More, now offer Open key account.
The agent itself receives the key, so give each agent its own account with a spend limit. If the agent offers no API-key sign-in, or refuses the key, the task ends with the reason. A task on an agent whose key account was disabled or deleted doesn't start until you bind another one.
Run a task on one
Pick the installed agent in a task's agent picker, or make it a project's default agent. See Start a task. Registry agents don't run on MicroVM nodes yet.
Agents that can't be installed
Some cards show a reason instead of Install:
- Needs key in environment, not supported: the agent takes its API key only from its environment, and Jaah never gives an agent a key that way.
- No Linux build in the registry: Jaah's nodes run Linux, and the registry offers no Linux build.
- No checksummed Linux build in the registry: the registry's Linux builds have no checksum, so Jaah can't verify them.
Remove one
- Select the Custom agents tab.
- Open the agent's ⋯ menu and choose Delete.
- Confirm with Delete.
An agent that tasks or projects still use can't be deleted. Choose Disable from the same menu instead.