[ AI tools · Development ]
Devin Clears the Chores. Engineers Keep the Judgment.
We hand Cognition’s Devin the well-specified, repetitive work: upgrades, small fixes and changes across many repositories. It opens the pull requests; our senior engineers review every one.
Sprint backlog: chores
6 open · 0 in review
- ENG-311Upgrade Node to 22 in billing-servicePR #901
- ENG-318Replace moment with date-fns in adminPR #902
- ENG-322Add retries to the webhook senderPR #903
- ENG-327Fix Sentry error: null user in exportPR #904
- ENG-330Remove the unused feature flagsPR #905
- ENG-334Add types to the reporting clientPR #906
Example sprint. Every pull request is reviewed by an engineer before merge.
An Autonomous Software Engineer, Now on the Desktop Too
Cognition’s Devin takes tickets and works through them on its own, and since the Windsurf acquisition it also lives in an editor. Four ways it shows up, playing on the right.
Cloud sessions
Devin works in its own cloud machine with a shell, editor and browser, from a ticket, a Slack message or its web app.
- $ git checkout -b fix/upload-timeout
- $ npm test · 3 failing
- Opened browser · reproduced the bug
- PR #602 opened for review
Example sessions. Hover to pause.
On the Desktop or in the Cloud
Runs on the engineer's machine, inside the editor formerly called Windsurf, with the engineer approving each step.
- Devin Desktop
Pairing on a new feature
The engineer drives and Devin works locally beside them, editing files and running tests on their machine.
- Devin Desktop
Understanding unfamiliar code
Devin explains an old module and maps its callers before anyone changes it.
- Devin cloud
One upgrade across forty repositories
Parallel cloud sessions open one pull request per repository, each with its CI result.
- Devin cloud
A Sentry error from a Slack thread
Tag Devin in the thread; it reproduces the error, writes a failing test and fixes it.
- Devin cloud
A codebase-wide security scan
Parallel agents search every service for a pattern and report each finding with a suggested fix.
What We Hand to Devin, and What We Never Do
Hand it to Devin
- Dependency and framework upgrades with a passing suite as the goal
- Bug fixes with clear reproduction steps
- The same change across many repositories
- Test backfills for modules with clear behavior
- Lint, type and deprecation cleanups
- First drafts of migrations an engineer will finish
Keep with an engineer
- Product decisions and anything with unclear requirements
- Architecture and data model changes
- Security-sensitive code paths without a specialist reviewing
- Work that needs systems Devin cannot reach
- Customer-facing copy and UX judgment
Playbooks Turn One Good Run Into a Hundred
Devin is only as consistent as its instructions. We write them once for each kind of task, then reuse them across repositories.
- 01PlaybooksStep-by-step instructions for a task type, such as an upgrade, with the checks that define done.
- 02KnowledgeFacts about your systems Devin should always know: how to run tests, where configs live, who owns what.
- 03Repository setupA prepared environment per repository, so every session starts with dependencies installed and tests passing.
- 04Review feedback loopComments from human review become updates to playbooks and knowledge, so the same mistake does not repeat.
Controls We Set Before Devin Touches a Repository
Repository access
Devin only sees the repositories and branches you grant, and never pushes to protected branches.
Your network
Enterprise plans can run Devin in your own VPC, so code and secrets stay inside your network.
Single sign-on
SSO and roles decide who can start sessions and approve their output.
Budgets
Usage is metered in agent compute units; we set limits per team and alerts on spend.
Session records
Every session keeps its plan, commands and changes, so a reviewer can see how a result was reached.
Secrets handling
Secrets are injected per repository and kept out of prompts, logs and commits.
[ Backlog review ]
Send Us Twenty Tickets. We Will Tell You Which Ten an Agent Can Do.
Book a Backlog ReviewTwo Questions Before Anyone Hires an Agent
What is slowing your team down?
Who reviews what agents write?
Packages from $1,500; custom projects from $8,000. Devin seats are bought from Cognition.
Dedicated Developer Trial
A senior engineer who runs Devin and other agents on your backlog for a month and reviews everything they produce.
$3,000 to $5,000/mo
1 month
Devin Questions
Open as many as you like.
Let's build your next product together
Book a free strategy call and leave with a clear plan and estimate. No commitment.
- 01Pick a time that suits you
- 0230 minutes on scope, stack, timeline and budget
- 03Fixed-price proposal, NDA on request