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

# Devin Bots

> Give a Devin Bot an outcome to own. It plans the work, starts Devin sessions, and keeps going until it's done.

You give a Bot an outcome to own in its chat. It plans the work, starts a Devin session for each piece, follows up on those sessions, and comes back to you when something needs you.

![Before: one request, Fix checkout, starts one Devin session that opens one pull request. After: one request, Own checkout, goes to a Bot that connects tools such as Slack, GitHub, and Linear and keeps many Devin sessions working.](https://mintcdn.com/cognitionai-enterprise/sRZisdw24ll7pC0S/images/bots/bots-before-after.svg?fit=max\&auto=format\&n=sRZisdw24ll7pC0S\&q=85\&s=a90954901c3a061149aeaa6b05c980fb)

Before: one request starts one session. After: one request goes to a Bot, which uses your connected tools and runs as many sessions as the work takes.

## How Bots work

* **Chat.** A Bot has one chat for everything it owns. You tell it the outcome you want there, and its reports come back there.
* **Sessions.** Each piece of work runs in its own child session with its own machine, the same as a session you start yourself. The Bot starts these sessions and monitors them. See [managed Devins](https://docs.devinenterprise.com/work-with-devin/advanced-capabilities.md#managed-devins).
* **Automations.** A Bot can run on a schedule or when something happens in your tools, without a message from you. See [Automations](#automations).
* **Needs you.** Approvals, decisions, and pull requests to review are collected in one list. See [What needs you](#what-needs-you).
* **Memory.** What the Bot learns is saved to its memory and used in later sessions. See [Instructions and memory](#instructions-and-memory).
* **Access.** A Bot has its own [connections and secrets](https://docs.devinenterprise.com/work-with-devin/bots/connections.md), separate from the people who message it, and you choose who can use it. See [Access and security](https://docs.devinenterprise.com/work-with-devin/bots/access-and-security.md).

## Create a Bot

In the sidebar's Bots section, click **Create new Bot**, pick a [template](#bot-templates) or **Start from scratch**, and name the Bot. Then tell it in the chat what outcome it owns:

```text theme={null}
You own the Android app now. Keep it at feature parity with iOS.
```

* A new Bot is private to you until it's [shared](https://docs.devinenterprise.com/work-with-devin/bots/access-and-security.md#share-a-bot).
* A Bot's work counts toward your plan's usage like any session. See [Usage limits](https://docs.devinenterprise.com/work-with-devin/bots/usage-limits.md).

A Devin session can also propose a new Bot when its work calls for one. The Bot is created only when you approve it.

### Bot templates

A template gives a new Bot a job it already knows how to do, such as a QA Engineer that tests each pull request in a browser or a Data Analyst that answers data questions with the chart and the query behind it. Pick one when you create a Bot, or browse **Template library** in the sidebar's Bots section or the public [Bot marketplace](https://devin.ai/bots/templates). You can also share your own Bot's instructions as a template. See [Templates](https://docs.devinenterprise.com/work-with-devin/bots/templates.md).

## Work with a Bot

Give a Bot an outcome to own, not a task to finish: "own checkout" rather than "fix the checkout button". The Bot plans the work, starts the sessions, and keeps going. When a session opens a pull request or needs a decision, the Bot reports back in the same chat.

After that, a message to the Bot is usually a check-in:

```text theme={null}
anything waiting on me?
```

You can also use the chat to change what the Bot is working toward or to answer what it asks you.

You can reach a Bot from:

* **The Devin web app.** Your Bots and the ones shared with you are in the sidebar's Bots section.
* **Slack.** Give the Bot its own Slack app so your team can @-mention it or DM it. See [Use a Devin Bot in Slack](https://docs.devinenterprise.com/work-with-devin/bots/slack.md).
* **iMessage.** Text the Bot from your phone. See [Use a Devin Bot in iMessage](https://docs.devinenterprise.com/work-with-devin/bots/imessage.md).

### What needs you

Items the Bot can't handle alone are collected under **Needs you**, which opens from the Bot's name at the top of its chat.

| Item | What you do |
| - | - |
| **Decision** | Pick one of the options. The Bot marks the one it recommends. |
| **Review PR** or **Merge PR** | Review or merge the pull request. |
| **Permission request** | Approve or reject a change the Bot can't make alone, such as new access, an automation, a network host, or a usage limit increase. |
| **Report** or **FYI** | Read it. |

You can also reply to an item in your own words, snooze it, or dismiss it.

A Bot asks before it takes on new access. When it needs one of your sign-ins, a secret, or a session, it shows an approval card that says what approving will share. See [how a Bot gets a grant](https://docs.devinenterprise.com/work-with-devin/bots/access-and-security.md#how-a-bot-gets-a-grant).

### Automations

Ask the Bot in chat to run something on a schedule or when something happens, for example a morning summary of open pull requests. The Bot sets up the [automation](https://docs.devinenterprise.com/product-guides/automations.md), and may ask you to approve it before it takes effect. The **Automations** page of the Bot's settings lists them, and you can pause, resume, or remove one there.

### Instructions and memory

A Bot works from instructions that people write and [memory](https://docs.devinenterprise.com/product-guides/memory.md) that the Bot writes itself.

* **Instructions** are what the Bot reads at the start of every session. People who can configure the Bot edit them on the **General** page of its settings.
* **Memory** is what the Bot saves as it works, such as your preferences, corrections, and project details. To change what it remembers, ask it in chat. The **Memory** page of the Bot's settings lists the files it wrote, and people who can configure the Bot can delete one.

Everyone who can use a Bot can read what it remembers, so a shared Bot's memory is shared too.

### Modes

A Bot has two modes: the one the Bot itself runs in, and the default for the sessions it starts. The mode picker in the Bot's chat box shows both when they differ, for example **Normal / Ultra**.

* **The Bot's mode.** Pick it in the mode picker, as you would for a session.
* **Child Capability.** In the same menu, sets the mode for the sessions the Bot starts. It starts on your organization's default mode, and only people who can configure the Bot can change it.

You can also ask the Bot in chat to use a different mode for any one session.

## Archive or delete a Bot

| Action | What it does |
| - | - |
| **Recycle** | Terminates the Bot's current session. A fresh one starts automatically while the Bot's page is open, or the next time the Bot is opened. It's in the menu of the Bot's chat. |
| **Archive** | Stops the Bot from responding and removes it from Bot lists. You can unarchive it later from **View all Bots**. Archiving removes the Bot's own Slack app from your workspace, so set Slack up again after you unarchive it. It also removes the access between the Bot and other Bots, and unarchiving doesn't restore it. See [Remove access between Bots](https://docs.devinenterprise.com/work-with-devin/bots/access-and-security.md#remove-access-between-bots). |
| **Delete** | Permanently deletes the Bot, its settings, and its sessions, along with its memory, automations, and tasks. This can't be undone. |

**Archive** and **Delete** are in the Bot's settings. Only the Bot's creator and roles with [**Manage Bots**](#enterprise-permissions), such as organization admins, see them.

## Enterprise permissions

Anyone who can use Devin sessions in an organization can create Bots and use the ones shared with them. Each Bot's sharing decides who can use, configure, or share that Bot. See [Access and security](https://docs.devinenterprise.com/work-with-devin/bots/access-and-security.md).

On Enterprise plans, three permissions in [custom roles](https://docs.devinenterprise.com/enterprise/security-access/custom-roles.md) also control Bots:

| Permission | What it allows |
| - | - |
| **Use Bots** | Create Bots and use the ones shared with you. The built-in roles that can use Devin sessions include it. Add it to a custom role to let its members use Bots. |
| **Manage Bots** | Share, archive, and delete any Bot in the organization, without access to its conversations. The built-in admin role includes it. |
| **Manage Bots across the enterprise** | Share, archive, and delete any Bot in every organization of the enterprise, without access to its conversations. It's an account-level permission. |

## Next steps

> [card] [Templates](https://docs.devinenterprise.com/work-with-devin/bots/templates.md)
>
> Start a Bot from a template, or share your own Bot's instructions as one.

> [card] [Access and security](https://docs.devinenterprise.com/work-with-devin/bots/access-and-security.md)
>
> Share a Bot, and understand who can use it, what it can reach, and how Bots hold grants.

> [card] [Connections and secrets](https://docs.devinenterprise.com/work-with-devin/bots/connections.md)
>
> Give a Bot the MCP servers, plugins, and secrets it needs.

> [card] [Slack](https://docs.devinenterprise.com/work-with-devin/bots/slack.md)
>
> Give a Bot its own Slack app so your team can @-mention it.

> [card] [iMessage](https://docs.devinenterprise.com/work-with-devin/bots/imessage.md)
>
> Text a Bot from your phone.

> [card] [Usage limits](https://docs.devinenterprise.com/work-with-devin/bots/usage-limits.md)
>
> Who pays for a Bot's usage and what its limit caps on each plan.


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