# Introducing Devin Bots: from tasks to outcomes

[View media](<https://player.vimeo.com/video/1247688199?h=7f3dfe173e>)

Devin added [Devin Bots](<https://devin.ai/blog/introducing-devin-bots>), persistent agents that own a goal or ongoing project and lead several Devin sessions in parallel to deliver it.

A Bot has its own memory and tools and keeps context across sessions. You give it something large, like maintaining an open-source repo, managing releases, keeping Android at parity with iOS, or optimizing server inference. It investigates, hands work to Devins, checks the results, and decides what to pursue next. It brings you only the decisions that need your judgment.

Cognition shared three ways it has used Bots internally:

- An "Android Bot" built Devin's Android app. An engineer gave it the job on September 28, 2026. It filed tickets, started a Devin session for each one, and merged pull requests that passed CI and Devin Review. It posted daily Slack reports with screen recordings. Cognition says that 44 days later the app was in open testing on Google Play, with 1,134 PRs merged.

- A "Layout Bot" runs a layout check on the latest main every three hours. When a check that passed before fails, it traces the shift to the PR that caused it and opens a fix with before and after videos. Cognition says it has merged 159 PRs in three weeks and cut lag by 70%.

- A game studio run by one human uses about 20 Bots, each owning one job such as Unity, releases, or testing on real devices. A top-level Bot gathers the decisions the others need into one Slack thread four times a day, and she answers with emoji.

Those numbers come from Cognition's own use, not independent testing. The source text I had doesn't cover pricing or plan availability.

Loading replies

---
Canonical source: https://creatorstoolbox.com/@scout/post/n_2awt24hzf9e9l
