---
updatedAt: 2026-09-16T22:54:10.000Z
agentTools:
  projectIndex: https://docs.redbird.io/llms.txt
---

# Add specialist AI agents

Manage the focused experts Autopilot can bring into your conversations — including ones you define yourself

## Introduction

Specialist agents are focused experts that Autopilot can bring into a conversation when a request falls in their area of expertise. You don't call them directly — Autopilot decides when a specialist is the right tool for what you asked, hands the work over, and brings the results back into your chat.

There are two kinds:

* **Redbird Specialists** — provided out of the box, like the **Data Science Specialist** used for forecasting and modeling.
* **Custom Specialists** — experts you define yourself, with your own rules for when they should step in, how they should think, and what they should do.

## Where specialists live

Open the **Resources** panel on the left and expand **Specialist AI Agents**. You'll see both groups, each specialist with an **on/off toggle**: switched on, Autopilot can bring that specialist into the conversation; switched off, it's excluded — without deleting anything.

![The Specialist AI Agents section: Redbird Specialists and Custom Specialists, each with a toggle](https://files.readme.io/9a7217bce6f5d9904a2a4365cafa76ca7a51946e23574f3a2db57b20cf3bafcc-01-specialists-panel.jpg)

<br />

## Add or edit a custom specialist

Click **Manage** next to Custom Specialists to open the Specialist Agents page. Your custom specialists are listed on the left — click **+ New specialist** to create one, or select one to edit it. (Redbird-provided specialists aren't edited here; they're managed for you and controlled through their toggle only.)

![The specialist edit view: Name, Description, and When to invoke](https://files.readme.io/1006372ccfc47cb93c9851d7204acfcc41567d85a1735cbe31e46fd377a07c85-02-specialist-edit-view.jpg)

<br />

Each specialist is defined by four fields:

* **Name** — what the specialist is called. (Its internal identifier is set when it's created and doesn't change afterward.)
* **Description** — one or two sentences on what this specialist is for.
* **When to invoke** — the important one: describe the requests, topics, and situations where Autopilot should consult this specialist — and anywhere it should *not*. Autopilot reads this on every message to decide when to bring the specialist in.
* **Logic** — the specialist's thinking style and rules for its scenarios. Specialists automatically get read-only tools for exploring your data and drafting plans; this field tells them how to apply those tools in your domain.

![The Logic field, with the specialist's rules for its domain](https://files.readme.io/d5e62ecb1ac64a87b0ba18bc654790e19bd817632c2954e1fec09c3edaeb71e3-03-specialist-logic-field.jpg)

<br />

Use **Save** to keep your changes, or **Delete** to remove a custom specialist entirely. If you just want a specialist to sit out for a while, use its toggle in the Resources panel instead — deleting removes its definition for good.

## Using a specialist

Once a specialist is toggled on, there's nothing more to set up: make requests as usual, and Autopilot brings the specialist in when its "when to invoke" description applies. You can also ask for one explicitly:

> Ask the data science specialist to forecast total sales for the next quarter

The specialist works in the open — narrating its steps and sharing its findings directly in your chat.

![A specialist working through an analysis in the conversation](https://files.readme.io/ecfd5a93d49f108ed268b95f67d7b55c8113d9dec1ccf035f8828c43720425b4-04-specialist-in-chat.jpg)

<br />

<Callout icon="📘" theme="info">
  **Good custom specialists are narrow.** The best "when to invoke" descriptions name specific request types ("when the user asks to add temperatures to a dataset based on month") rather than broad topics — the crisper the trigger, the more reliably Autopilot brings the right expert in at the right time.
</Callout>