Devin Bots (2026): What They Are and How to Set One Up
By Antigravity Skills editorial team · Last updated
Short answer: A Devin Bot is an agent inside Cognition's Devin that owns an outcome, not a single task. Per Devin's docs, it plans the work, starts a separate Devin session for each piece, follows up and reports in one chat. You create one in the Bots section of the Devin web app and reach it by web, Slack or iMessage.
Unofficial guide. Antigravity Skills is not affiliated with Cognition or Devin. Everything about Devin below was read on the pages listed under Sources on November 22, 2026. Devin changes often, so check the docs before you rely on a step. We did not run a Devin Bot ourselves, so how well one performs is not something this page can tell you.
What are Devin Bots?
Devin is described on its own site as an autonomous software engineer that runs in the cloud or on your machine. A Bot is a layer above a single Devin session. The docs say each Bot has one chat for everything it owns, and each piece of work runs in its own child session with its own machine. You tell the Bot what outcome it owns, for example keeping an Android app at feature parity with iOS (the docs' own example), and later messages are usually check-ins.
Bots are not the same as tagging @Devin
The docs keep two things separate. The main Slack integration lets you tag @Devin in a thread to start a session. A Bot can have its own Slack app and handle, so your team can mention or message a Bot that owns one job. Bots have their own setup, approval and permissions.
Other things called "Devin bot"
Search results for the phrase also show unrelated items, such as a Devin web-crawler entry in bot directories and a community Discord bot. We did not open those, and this page covers only the Bots feature in the Devin docs.
How Devin Bots work
According to the Bots page, a Bot can:
- Run sessions for you. It starts a Devin session per piece of work and follows up on each one.
- Ask you when it is stuck. Items it cannot handle alone appear under "Needs you": a decision to pick, a pull request to review or merge, a permission request, or a report to read.
- Run on a schedule or on events. You ask it in chat to set up an automation, such as a morning summary of open pull requests. It may ask you to approve it first, and the Automations page in the Bot's settings lets you pause, resume or remove it.
- Keep instructions and memory. People who can configure the Bot write instructions that are read at the start of every session. The Bot writes memory as it works, and everyone who can use a shared Bot can read that memory.
What a Bot is, in one table
| Item | What the docs say (checked 2026-11-22) |
|---|---|
| What you give it | An outcome to own, not one task |
| Where work runs | One child Devin session per piece of work, each with its own machine |
| How you reach it | Devin web app, Slack, iMessage |
| Who can create one | Anyone who can use Devin sessions in the organization |
| Default visibility | Private to you until you share it |
| Usage | Counts toward your plan's usage like any session |
| Price | Not stated on the Bots page |
How to set up a Devin Bot
These are the steps the docs give. We have not run them.
- Create the Bot. In the sidebar's Bots section, click Create new Bot, then choose a template or Start from scratch, and name it. The docs' template examples are a QA Engineer that tests each pull request in a browser and a Data Analyst that answers data questions with a chart and the query behind it.
- Give it an outcome. Tell it in chat what it owns.
- Share it if you want others to use it. A new Bot is private until shared. Each Bot's sharing setting decides who can use, configure or share it.
- Add Slack (optional). Connect Slack to your Devin organization first. Only the Bot's creator can authorize Devin in Slack and add the Bot's app. On the Bot's Slack page you authorize, choose the handle people will @-mention, and select channels (for private channels, run
/invite @handlein Slack). By default only people the Bot is shared with can message it. If your workspace needs admin approval for apps, a Slack admin must install it. - Add iMessage (optional). The docs say you can text a Bot from your phone and link a separate iMessage page. We did not read that page, so check it for steps.
Archive and delete
The docs say archiving stops responses, hides the Bot and removes its Slack app, so Slack must be set up again. Deleting permanently removes the Bot, its settings, sessions, memory, automations and tasks and cannot be undone.
Enterprise permissions
On Enterprise plans the docs list three custom-role permissions: Use Bots, Manage Bots and Manage Bots across the enterprise. The built-in admin role includes the second.
What we could not verify
- Price and plan limits. Neither devin.ai nor the Bots page we read states a price for Bots. The Bots page links to a Usage limits page that we did not read.
- Availability or beta status. The page does not mention either.
- Independent reporting. A New Stack article on Devin Bots appears in search results, but our fetch of it returned HTTP 403, so we used nothing from it.
Devin Bots compared with Claude Code or Antigravity with skills
These tools solve a similar problem in different ways. This comparison is our reading of the public docs, not a benchmark.
| Devin Bots | Claude Code or Antigravity with skills | |
|---|---|---|
| Where it runs | Cognition's Devin service, in the cloud or on your machine | In your own terminal or editor session |
| Unit of work | An outcome a Bot owns across many sessions | A task in a session you start and watch |
| Behaviour is shaped by | Bot instructions and memory kept in Devin | SKILL.md folders and project instructions you can read and edit as files |
| Reach | Web app, Slack, iMessage | Your editor or terminal |
| Cost | Counts toward your Devin plan; no Bot price stated | Depends on the agent and model you use |
The practical difference is where the know-how lives. With a skill, the instructions are a plain folder you keep in your own repository and can move between agents. With a Bot, the instructions and memory live inside Devin. If you want to understand skills first, read what Antigravity Skills are, then browse the skills library. For where each agent looks for a skill folder, see install skills.
FAQ
What are Devin Bots?
They are agents in Cognition's Devin that own an outcome over time. A Bot plans work, starts Devin sessions for each piece, follows up and reports in one chat, according to the Devin docs.
How do I create a Devin Bot?
Open the Bots section in the Devin sidebar, click Create new Bot, pick a template or start from scratch, name it and tell it what outcome it owns. It stays private until you share it.
Are Devin Bots free, and are they the same as @Devin in Slack?
We could not find a price for Bots on the pages we read; their work counts toward your plan's usage. They are not the same as @Devin: the Slack integration starts a session when you tag @Devin, while a Bot can have its own Slack handle and owns a goal.
Sources
- Devin Bots (Devin docs), read November 22, 2026
- Bots in Slack (Devin docs), read November 22, 2026
- Devin in Slack (Devin docs), read November 22, 2026
- Devin docs home, read November 22, 2026
- devin.ai, read November 22, 2026