> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/agent-builder.md).

# Agent builder

The Agent builder is build mode for an agent: the Chat, Pipeline, Agent, Triggers and Activity tabs, Deploy, and how it relates to the live agent.

The Agent builder is **build mode** for an agent: where you change it. Your team uses the [live agent](https://docs.riff.ai/reference/agent-builder/the-live-agent.md); nothing you do in build mode reaches them until you [deploy](https://docs.riff.ai/reference/agent-builder/deploy-an-agent.md).

**To open it:** click **Agents** in the left sidebar, open the agent, then click **Edit agent**, top right. A new agent opens here straight after **Create agent**. To create one, see [Build your first agent](https://docs.riff.ai/get-started/quickstart-agent-v2.md).

## The tabs

| Tab                                                                           | What it is                                                                       |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [Chat](https://docs.riff.ai/reference/agent-builder/chat.md)                  | The build chat. Tell the Riff agent what to change.                              |
| [Pipeline](https://docs.riff.ai/reference/agent-builder/pipeline.md)          | Test tasks in build mode, kept separate from live tasks. Autonomous agents only. |
| [Agent](https://docs.riff.ai/reference/agent-builder/profile.md)              | Everything the agent is made of. Edit rules and tool permissions here.           |
| [Triggers](https://docs.riff.ai/reference/shared/triggers-and-automations.md) | What brings in work: email and schedules. Autonomous agents only.                |
| [Activity](https://docs.riff.ai/reference/agent-builder/activity.md)          | Every run, its logs, and performance metrics.                                    |

An **Assistant** has **Chat**, **Agent** and **Activity** only.

More tabs open with **+**: [Integrations](https://docs.riff.ai/reference/shared/integrations.md), [Storage](https://docs.riff.ai/reference/shared/storage.md), [Secrets](https://docs.riff.ai/reference/shared/secrets.md), Access and [Version History](https://docs.riff.ai/reference/shared/version-history.md).

## The top bar

* **Build**, beside the agent's name, says you are in build mode.
* **Draft** means the agent has never been deployed. An orange **Changes to deploy** means build mode has changes that aren't live yet.
* **Deploy** makes your changes live. See [Deploy an agent](https://docs.riff.ai/reference/agent-builder/deploy-an-agent.md).
* **View live** opens the live agent.

## Related

* [Rules](https://docs.riff.ai/reference/agent-builder/rules.md)
* [Tool permissions and approvals](https://docs.riff.ai/reference/agent-builder/tool-permissions-and-approvals.md)
* [Prompts to copy](https://docs.riff.ai/reference/agent-builder/prompts-to-copy.md)
* [The Riff agent](https://docs.riff.ai/reference/riff-agent.md): the assistant you chat with in build mode, which is not the same as the agent you build.


---

# 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.riff.ai/reference/agent-builder.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.
