> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/agents-in-the-workspace/custom-subagents.md).

# Custom subagents

Define your own specialist agents for Evolve Mode to delegate to.

A **custom subagent** is a specialist you define for [Evolve Mode](/zerve-docs/agents-in-the-workspace/evolve-mode.md) to delegate to, alongside the built-in [specialists](/zerve-docs/agents-in-the-workspace/evolve-mode/specialists.md). Use one for work your team does often and wants done a particular way, such as reconciling positions against a custodian file.

Manage custom subagents in **Settings → Subagents**.

{% hint style="info" %}
Custom subagents may not be enabled for every organization yet. If you don't see **Subagents** in Settings, contact your Zerve administrator.
{% endhint %}

## Creating a subagent

Each custom subagent has:

| Setting         | Details                                                                                                   |
| --------------- | --------------------------------------------------------------------------------------------------------- |
| **Name**        | What it's called                                                                                          |
| **Description** | What the subagent should do. This becomes its instructions, so write it as you would brief a colleague.   |
| **Model**       | The model it uses. The default, **Inherit (org default)**, uses your organization's default coding model. |
| **Tools**       | Which tools it may use, chosen from groups of tools. A subagent needs at least one.                       |

Give each subagent only the tools it needs. A subagent that only reviews code, for example, doesn't need tools that change the notebook.

If a subagent's model isn't available in your organization, it's marked **Model unavailable in this org**. Choose a different model, or ask an admin to enable it. See [Model settings](/zerve-docs/administration/model-settings.md).

## Using a subagent

Custom subagents can only be used in **Evolve Mode**. In the composer, open the **+** menu and select the subagent for Evolve Mode to use. Evolve Mode then delegates to it as it would to any other specialist.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/agents-in-the-workspace/custom-subagents.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.