# Add agents from the ACP Registry

> Install the built-in agents, any agent from the ACP Registry, or your own.

Source: https://sesh.codes/docs/more-agents/

Sesh talks to agents through the Agent Client Protocol (ACP). Claude Code, Codex, Gemini CLI and Cursor are built in. Any other agent in the ACP Registry, or any ACP agent you have, can be added too. Agents are installed per machine.

## Get a built-in agent

1. Open **Settings › Machines** and click **Details…** next to the machine.
2. Under **Agents**, click **Get** next to Claude Code, Codex, Gemini CLI or Cursor.
3. When it's done, click the agent, then **Sign In…** next to **Account**.

Sign-in opens the agent's own page in your browser, or gives you a code to enter. Some agents also take an API key; Sesh saves it as a variable on that machine.

## Add one from the ACP Registry

1. In the machine's **Details…**, click **Add an Agent…**.
2. Search the list, then click **Get**.

Agents that are built in say **Built In**; get those from the agent list instead. Ones you already have say **Added**, or **Update** when there's a newer version. Right-click a row and choose **Open Website** to learn more about it.

## Add your own

1. In **Add an Agent…**, click **Custom…**.
2. Enter a **Name** and the full path to the agent's program on that machine.
3. For a script, enter its interpreter too, such as `node`.
4. Click **Add**.

## Run an agent inside your own sandbox

Already sandbox your agents with a wrapper like [Agent Safehouse](https://agent-safehouse.dev/)? Sesh can launch them through it.

1. In the machine's **Details…**, click the agent.
2. Next to **Launch With**, click **Edit…**.
3. Enter the command to put in front of the agent, such as `safehouse --env`.
4. Click **Save**. Sesh tries the command first and shows anything it gets in the way of.

The command must:

1. Run the command Sesh adds after it, with its input and output untouched, and print nothing else to the output.
2. Keep Sesh's environment. For Agent Safehouse, add `--env`.
3. Let the agent read the `tools` and `agents` folders in `~/Library/Application Support/Sesh` (`~/.local/share/sesh` on Linux), and run Sesh's `seshd`.

In Autonomous sessions, your command is the agent's sandbox, and Sesh's own steps aside (one sandbox can't start inside another). Clear the field to launch the agent directly again.

## Remove an agent

Click the agent in **Details…** and choose **Remove Agent…**. Its sessions keep their history, but can't start it again. This works for registry and custom agents; built-in ones stay listed.

## Good to know

- Agents from the registry or added by hand can't be signed in from Sesh. Sign in on the machine, in a terminal.
- Some registry agents need `uv` on the machine. Sesh says **Needs uv** when it's missing.
- Sesh doesn't check the registry for updates in the background. Open **Add an Agent…** and click **Refresh**.
- On iPhone and iPad, registry agents show their initial instead of their icon.
