Starting today, Devin can break down large tasks and delegate them to a team of managed Devins that work in parallel.
Each managed Devin is a full Devin, running in its own isolated virtual machine with its own terminal, browser, and development environment. Each one can independently run shell commands, execute tests, and verify its own changes before reporting back. Each has its own session link, so you can inspect its work or message it directly.
The main Devin session acts as a coordinator: it scopes the work, assigns each piece to a managed Devin, monitors progress, resolves any conflicts, and compiles the results.
This matters because when one agent tries to handle too many things in a single session, context accumulates, focus degrades, and the quality of each subtask suffers. Each managed Devin gets a clean slate, a narrow focus, its own shell, and its own test runner. And they all run in parallel.
Devin can also read the full trajectories of its managed Devins to understand what worked, what didn't, and where they got stuck, and use that to improve how it breaks down the next task. Over time, each managed Devin makes the next one more effective.
What Devin can do
Spin up managed Devins: Devin breaks a task into scoped pieces and delegates each to a separate session
Message child sessions: send instructions, context, or corrections to any managed Devin mid-task
Monitor ACU consumption: track how much compute each child session is using
Put child sessions to sleep or terminate them: pause or stop any managed Devin that's done or going off track
Schedule messages to itself: set up follow-ups and checkpoints so the coordinator stays on top of progress
Try it now
Here are a few tasks where managed Devins can have an immediate impact. Click any prompt to open it directly in Devin.