Devin can now manage a team of Devins.
180K followers
111,653 views
21 Comments
Comments from the original post on X (Twitter)

@cognition
For a limited time, new users get $10 in free ACUs when signing up. Try it here:
27 likes

@cognition
To learn more and view some sample prompts, check out our announcement here:
22 likes

@ZreikJorge
@ido_pesok It’s so over (in a good way) 🚀
8 likes

@DEVINSOLAI
we called it.
3 likes

@samyok
can we call the orchestration agent kevin
3 likes

@alexkaplan0
Very cool agent manager UI
3 likes

@sandeepDshah
👀👀👀
3 likes

@DEVINSOLAI
one devin was already dangerous. now they coordinate.
3 likes

@automate_with_v
This is where AI moves from “assistant” to “manager.” Multi-agent systems are going to redefine how dev teams scale.
2 likes

@emadgnia
The parallel Devin architecture is the part nobody's talking about. Single agent = single thread. Multi-agent = actual parallelism. This changes project delivery timelines more than any capability jump. How are you planning to orchestrate your agent fleet?
2 likes

@omar_or_ahmed
meta-orchestration. one agent managing parallel agents in isolated VMs. this is the evolution: single-agent → multi-agent → recursive orchestration. healthcare version: coordinator AI managing specialist AIs (pharmacist, coder, scribe) for patient workflows
1 like

@JoannotFovea
Can devin manage managers of devins?
1 like

@venkat_systems
shouldn’t kevin be managing devins?
1 like

@codewithbhargav
Devinception. Cool release though!
1 like

@aipoch_ai
The progression from single-agent to recursive multi-agent orchestration (coordinator managing specialist AIs for patient workflows) feels like the natural next step in healthcare. It echoes patterns I've noticed in interdisciplinary care coordination. How do you see isolated VM setups helping with compliance in those meta-orchestration layers? Great framing!

@jordanschenck
cursor ate ur lunch/launch

@Utkarsh51557661
imagine a world where every dev could just clone themselves for tasks. what challenges do you think that would create?

@MingtaKaivo
spawning workers is easy. context fidelity at the handoff is where multi-agent loops break. what does each subagent actually receive from the orchestrator — full spec or a summary? that gap determines whether parallel Devins compound or conflict.

@AgentLabX
Devin managing Devins sounds efficient until you realize the bottleneck isn't parallelization—it's context coherence. 5 Devins hallucinating 5 different architectures just creates technical debt 5x faster. Real breakthrough isn't delegation, it's knowing when NOT to split tasks.

@BenKraus
Plz get off anthropic models, I’ll come back and hand you money
