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.
- Automations. A Bot can run on a schedule or when something happens in your tools, without a message from you. See Automations.
- Needs you. Approvals, decisions, and pull requests to review are collected in one list. See What needs you.
- Memory. What the Bot learns is saved to its memory and used in later sessions. See Instructions and memory.
- Access. A Bot has its own connections and secrets, separate from the people who message it, and you choose who can use it. See Access and security.
Create a Bot
In the sidebar’s Bots section, click Create new Bot, pick a template or Start from scratch, and name the Bot. Then tell it in the chat what outcome it owns:- A new Bot is private to you until it’s shared.
- A Bot’s work counts toward your plan’s usage like any session. See Usage limits.
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. You can also share your own Bot’s instructions as a template. See Templates.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:- 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.
- iMessage. Text the Bot from your phone. See Use a Devin Bot in iMessage.
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.
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.
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, 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 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.
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.
Archive or delete a Bot
Archive and Delete are in the Bot’s settings. Only the Bot’s creator and roles with Manage Bots, 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. On Enterprise plans, three permissions in custom roles also control Bots:Next steps
Templates
Start a Bot from a template, or share your own Bot’s instructions as one.
Access and security
Share a Bot, and understand who can use it, what it can reach, and how Bots hold grants.
Connections and secrets
Give a Bot the MCP servers, plugins, and secrets it needs.
Slack
Give a Bot its own Slack app so your team can @-mention it.
iMessage
Text a Bot from your phone.
Usage limits
Who pays for a Bot’s usage and what its limit caps on each plan.

