Reproducing Devin Bots — a field guide

Everything publicly documented about how the flagship Devin Bots were set up, condensed into recipes you can recreate. Sources: Cognition’s launch post (Nov 17, 2026), the Bots docs, the Fortune exclusive, and Jenny Xu’s SuperJennyStack thread.

How a Bot works (mechanics)

From the docs:

  1. Create — sidebar → Bots → Create new Bot → pick a template or Start from scratch. New Bots are private until shared.
  2. Outcome prompt — the first message assigns ownership: You own the Android app now. Keep it at feature parity with iOS. Give it a goal, not a task.
  3. Sessions — the Bot files its own tickets and runs one Devin session per piece, each on its own cloud machine.
  4. Automations — ask the Bot in chat to run something on a schedule or trigger (e.g. “morning summary of open PRs”). It proposes the automation; you approve once.
  5. Needs you — decisions, PR reviews, permission requests and reports land in one list; the Bot marks its recommended option.
  6. Instructions & memory — humans edit instructions (read at every session start); the Bot writes its own memory files as it learns.
  7. Surfaces — give the Bot its own Slack app for @-mentions/DMs, or text it on iMessage.
  8. Grants — Bot A can be granted read/message access to Bot B; this is how bots hand work to each other.

Check-in pattern: anything waiting on me?

Recipe 1 — Product-owner Bot (Android Bot)

Outcome: build and then own a whole product surface.

Recipe 2 — Scheduled-check Bot (Layout Bot)

Outcome: own a recurring quality check and the fixes it uncovers.

Recipe 3 — Multi-bot org (SuperJennyStack)

Outcome: a whole business run by a Bot hierarchy; the human decides, emoji-style.

Jenny Xu’s game studio — ~20 Bots, each owning one job. The stack as she published it:

Bot Owns
SuperJenny Orchestration: delegates to all others, compiles their asks into one thread; trained on her personality/quirks
SuperPM Ranked daily fix list from metrics + store reviews + trends
SuperRelease Weekly build, ready for store submission Friday
SuperQA Real-device tests with video proof
SuperSupport Drafts every store-review reply for approval; helps players overnight

Remaining ~15 Bots cover development, Unity, UI, iOS, Android, analytics, etc.

Recipe 4 — One-job Bots (official template patterns)

Each official template encodes one reproducible loop:

Template Loop Cadence
Software Factory Finds bugs/polish/perf/refactors in an area you name → one small PR each w/ proof; learns from your merge/close decisions Continuous
Product Engineer Ticket → tested PR → through review Per ticket
QA Engineer Tests each PR in a real browser, posts video + pass/fail Per PR
Anomaly Watcher Sweeps product + business data for unwatched problems, posts findings w/ owner 2×/day
Code Reaper Finds dead code, removes it one safe PR at a time w/ justification Weekly
Chief of Staff Watches channels, posts updates, delegates + tracks to done Continuous
Migration Engineer Owns one big migration as small tracked PRs; reports progress & blockers Continuous
Latency Optimizer Finds slowest endpoints/jobs/queries, fixes worst one w/ before/after numbers Weekly
iOS / Android Engineer Ticket → PR w/ tests + installable build (TestFlight / internal testing) Per ticket
Internal Tools Engineer Builds + runs + updates an internal tool on request On demand
Data Analyst Answers data questions w/ chart + underlying query + caveats On demand
Devin Coach Weekly report: where Devin got stuck + one fix each (note, skill, setup change) Weekly
Code Health Engineer Stale flags, old deps, CVEs → small safe PRs Monthly
Technical Writer Keeps repo wikis/diagrams in step with main after merges Per merge
Compliance Engineer Collects control evidence from code, warns when a control lapses Continuous

Reported usage beyond Cognition

Named beta deployments (all reported Nov 17–18, 2026, day-one of launch):

From the launch video and early-user reports (daily.dev summary):

Operating tips (what the successful ones share)


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