> For the complete documentation index, see [llms.txt](https://docs.helmut.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.cloud/high5/spaces-in-high5/agent-pools.md).

# Agent Pools

### Viewing Agent Pools

To view agent pools:

1. Navigate to your High5 space.
2. Click **Agent Pools** in the left sidebar.

The Agent Pools page displays a list of all pools in the current space.

The list includes:

* **Pool Name** – The name of the agent pool
* **Targets** – The agents or execution targets assigned to the pool (if configured)

You can use the **Search** and **Filter** options to locate specific pools.

<figure><img src="/files/NMtC9KNHZypKzyBHBod3" alt=""><figcaption></figcaption></figure>

### Creating a New Agent Pool

To create a new agent pool:

1. Click **+ Add pool** in the top-right corner.
2. Enter a name for the pool.
3. Click on "Create" button.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.cloud/high5/spaces-in-high5/agent-pools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.