---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/ai/ola/get-started#article
headline: Get started with Ola
description: ""
url: https://www.twilio.com/docs/ai/ola/get-started
inLanguage: en
dateModified: 2026-10-05T19:07:43.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Get started with Ola

> \[!NOTE]

Ola provides the communication and trust layer that lets you delegate more to your AI agents.
Through Ola, you can talk to agents, set the agents' boundaries, and approve the agent's actions across mobile and desktop.

## Time to complete

About 5 minutes.

## Expected outcomes

* You connected your agent to Ola.
* You can send messages and approve actions for your agent in Ola.

## Prerequisites

* [Create an Ola account][olachat.com].
  * Install and activate an AI agent.
  * Ola supports Hermes, OpenClaw, and Claude Code (2.1.81 or later) agents using plugins.
  * Any [*Model Context Protocol* (MCP)][mcp]-capable host can connect using MCP.

## Connect your agent

To connect your agents to Ola, follow these steps:

1. Go to the **Agents** page.
2. Click **Connect an agent**.
3. Name the connection.
4. Choose your host.\
   Ola issues an API key beginning `ak_`.
5. Copy the API key before you continue. Ola displays it once.
6. Complete the connection using one of two methods:

   ## Plugin

   The plugin includes the MCP connection and the consent gate.

   * The plugin opens and maintains a connection to Ola. Messages reach your agent as soon as you send them over that connection.
   * Before the tool runs, the agent checks your configured permissions to determine whether or not it needs your approval.

   ## MCP

   The MCP connection doesn't include the consent gate.

   * Your agents can request approval for their actions, but adherence is not enforced.
   * Configure message delivery using a webhook or polling the agent's Ola inbox.

## Install Ola

One command per host. Set `OLA_API_KEY=` after the pipe (`|`), not before `curl`, as shown in the provided commands. Setting it before `curl` scopes the variable to that command alone, and the installer exits with `OLA_API_KEY is not set`.

## Claude Code

1. To install into a single project or directory rather than for your user, set `OLA_PLUGIN_SCOPE=project` before running the installer.
2. To install the plugin, register the MCP server, and write your key and gateway URL into your settings, run the following command:

   ```bash
   curl -fsSL https://olachat.com/install/claude-code.sh |\
   OLA_API_KEY=ak_your_key_here bash
   ```
3. Start your session with this flag:
4. Restart any running sessions. Claude Code [Channels][] are in research preview, so the flag is required until the feature ships generally.

## OpenClaw

To install the plugin, register the MCP server, enable the consent gate, and configure message delivery, run the following command in your command line:

```bash
curl -fsSL https://olachat.com/install/openclaw.sh | OLA_API_KEY=ak_your_key_here bash
```

## Hermes

1. To install the plugin, register the MCP server, enable the consent gate, and configure message delivery, run the following command in your command line:

   ```bash
   curl -fsSL https://olachat.com/install/hermes.sh | OLA_API_KEY=ak_your_key_here bash
   ```

   This command also enables Hermes' `terminal`, `file`, and `code_execution` toolsets on the webhook platform.
2. Run Hermes in gateway mode with `hermes gateway run` (foreground) or `hermes gateway start` (background service).

   Other session modes don't support message delivery.

## No plugin

Use this for a host without a plugin. If you installed a plugin, it wrote your MCP configuration. Never add a second entry: two copies of your key that drift apart make your plugin's gate read the key as invalid and stop holding tool calls for approval.

```json
{
  "mcpServers": {
    "ola": {
      "type": "http",
      "url": "https://olachat.com/mcp",
      "headers": {
        "Authorization": "Bearer ak_your_key_here"
      }
    }
  }
}
```

* Ola registers its tools under their bare names like `get_inbox` and `send_message`.
* Hosts add their namespace. Claude Code exposes them as `mcp__ola__get_inbox`.
* Send instructions to your agent using the bare names.

## Receive messages

A plugin opens its own connection to Ola. As messages get sent, they reach the agent. Without one, you have two options:

* **Use a webhook**: Set a callback URL under **Webhook delivery** in the agent's details. Ola sends a `POST` request with each message to the callback URL. The agent webhook secret signs these messages. This URL requires a public address using HTTPS, so any local listener needs a tunnel.
* **Use a prompt**: Have the agent check its own inbox for an instruction in its system prompt that resembles the following command:

```markdown
## Check Ola for messages

Check Ola for messages and reply:

1. Call `get_inbox`. If any conversation has `"has_unread_human_reply": true`, proceed.
2. To read the thread, call `get_messages` with that conversation's `grant_id`.
3. Reply with `send_message` using the `human_id` from the inbox entry, not the `grant_id`.
```

## Turn on notifications

To receive input or approval notifications from your agent on your device, follow these steps:

1. **Install the app.** Ola prompts you with the steps for your browser and device. The iPhone requires the app.
2. **Allow notifications.** Tap **Enable** on the notification banner, in the sidebar on desktop or at the top of the screen on mobile.
3. **Choose what notifies you.** Under Profile, **Push notifications** has a switch for each intent type: **Inform**, **Collect**, and **Authorize**.

If you dismissed the banner, allow notifications for [olachat.com][] in your browser's site settings and reload Ola. It picks up the permission on the next load.

## Create your first intent

Ask your agent to take an action it isn't auto-approved to do, such as writing to a file or calling an external MCP tool.

An authorization card appears in the thread and a notification reaches your device. Approve it, and the action runs. Decline it, and your agent is blocked and moves on.

After approving, click **Don't ask me again for this**. This creates a custom rule where Ola only asks about actions you want to review going forward. To add and edit rules, go to your agent's **Settings**, under **Intent settings** > **Authorize**.

Having trouble? Contact us at `twilio_forward_support@twilio.com`.

[olachat.com]: https://olachat.com

[mcp]: https://modelcontextprotocol.io/docs/2026-07-28/getting-started/intro

[channels]: https://code.claude.com/docs/en/channels-reference