Anatomy of a Devin Bot

A deep dive into how Devin Bots actually work under the documented mechanics — for anyone evaluating, reproducing, or writing about them. Everything below is sourced from the official docs, the launch post, or named public deployments; each claim carries its source.

The ownership model

A Bot is defined by an outcome prompt — a standing assignment, not a task queue entry. The canonical example is the Android Bot’s prompt: “your job is to product manage the android app.” From that single sentence the Bot decomposed the outcome into tickets it authored itself, then ran a Devin session per ticket (launch post).

The operating loop:

outcome prompt → bot plans work → spawns Devin session per unit →
PRs land (or escalate) → memory updates → repeat

Key difference from a one-shot session: the Bot persists. The Android Bot ran 44 days on one assignment; the human sent 183 messages total, with a 22-day silent stretch where the Bot self-directed entirely (X).

The six documented mechanisms

Mechanism What it does Observed in
Chat The primary interface — you talk to the Bot like a teammate, in Devin, Slack, or iMessage All deployments
Sessions Each unit of work runs as a normal Devin session the Bot starts and supervises; you can open any session to inspect Android Bot (1,134 sessions→PRs)
Needs you The Bot’s escalation channel — it surfaces only decisions requiring human judgment, not status noise SuperJennyStack (emoji-only human replies)
Memory A persistent, editable store the Bot accumulates — preferences, decisions, conventions — carried across weeks Android Bot (44-day single assignment); Harvey Phil (memory + decision logs as the steering layer)
Grants Bot-to-bot handoffs: a Bot can delegate a unit of work to another Bot with the right scope Documented grant flow: QA Bot finds bug → grants fix to Dev Bot → re-tests → PM Bot reports
Slack app Each Bot gets its own Slack presence so channels can address it like a person tigsbot (one Slack channel per project)

What the public numbers actually show

Metric Deployment Source
1,134 merged PRs / 344,651 lines Kotlin / 2,841 screenshot tests Android Bot, 44 days launch post
88% of PRs self-merged Android Bot launch post
159 PRs in 3 weeks, jank −70% Layout Bot launch post
~50 → 1,900 PRs/week, studio revenue ×6 SuperJennyStack Jenny Xu
1M+ lines Rust+TS in 3 weeks, zero human engineers Harvey Phil Gabe Pereyra
4.5× more PRs merged per message (beta-wide) 1,000+ beta testers Fortune
2,000+ PRs/week merged at Cognition; 40× merge throughput; 1,000+ PRs from one autonomous goal Cognition internal Fortune
Up to 2.5× throughput per GPU Decagon AutoResearch Decagon

Patterns that recur across deployments

Known boundaries

Sources


← built-with-devin · build-with-devin