> ## Documentation Index
> Fetch the complete documentation index at: https://docs.helloleo.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# AI Agents

> Reusable AI assistants that work on your connected systems

An agent is an AI assistant you configure once and reuse: it holds a model, a set of integrations, a persona, and the permission rules that decide what it may touch. Attach it to a project, chat with it directly, reach it on WhatsApp, or let it run on a schedule.

Below, an agent reads new orders out of an Outlook inbox, looks the customers and products up in Odoo, and creates the draft sales orders.

<Frame>
  <video autoPlay muted loop playsInline src="https://cdn.helloleo.dev/tutorials/docs-agents.mp4" poster="https://cdn.helloleo.dev/tutorials/docs-agents-poster.png" />
</Frame>

<Note>
  Available on **Leo Business** and above. Agents consume [AI tokens](/getting-started/credits-system), a meter separate from your build credits.
</Note>

## Create an agent

Go to **Agents** in the sidebar and click **New agent**. There is no form: the agent is created with defaults and you land straight in its chat. You shape it from there, in the sidebar:

| Field | What it is |
| - | - |
| **Name** | How the agent appears everywhere |
| **Description** | One line on what it does |
| **Model** | Which Claude model runs it |
| **System prompt** | Its persona and standing instructions |
| **Integrations** | Which systems it may reach (Odoo, NetSuite, Microsoft 365, and the connector network) |
| **Workspace** | Which workspace it belongs to |

Connect an integration from the **Integrations** panel, then ask it something real against your data:

```
List the 5 most recent sales orders with their customer and total.
```

If it answers from your live system, it is configured correctly.

<Note>
  The agent declares which **types** of integration it needs. The credentials stay on the project, so the same agent can run against a staging Odoo on one project and production on another.
</Note>

## Permissions

An agent's rules are method-level per model: read allowed, write denied, and so on. A method that is not listed is refused. This is what makes it safe to expose an agent to people who are not your team. See [HelloLeo AI](/features/helloleo-ai).

## The agent's sections

Opening an agent gives you six sections, and its usage for the month (runs, AI tokens, integration credits) at the bottom of the sidebar.

| Section | What it is for |
| - | - |
| **Chat** | Talk to the agent, and read what its automations produced |
| **Integrations** | Connect the systems it may reach |
| **Access** | Who can reach it, and on which channels |
| **Automations** | Its scheduled tasks. See [Automations](/features/automations) |
| **Customize** | Name, description, model, system prompt, workspace |
| **Permissions** | What it may read and write, model by model |

## Reaching the agent

* **In a project** — attach it under Project Settings → HelloLeo AI, and it becomes the assistant inside your app
* **In the dashboard** — its own chat page
* **On WhatsApp** — see [Channels](#channels)
* **On a schedule** — see [Automations](/features/automations)

## Channels

An agent can be reached from outside HelloLeo. Open the agent and use the **WhatsApp** block: it shows a QR code and an enrollment code.

Whoever scans it and sends that code binds their phone to the agent, and their number appears under **Connected phones**. Anyone who has not enrolled is ignored, silently. That is deliberate: the agent has write access to your ERP, and a phone number is trivially claimed.

Regenerate the code to invalidate the old QR, or pause the channel without deleting the bindings. Messages received on WhatsApp also show up in the agent's chat in the app.

<Note>
  WhatsApp needs a number configured on the instance by an admin. Outlook, Teams and SharePoint go through the app catalog instead, like any other integration.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.