Skip navigation
Devin can now manage a team of Devins.
0:00 / 1:29

Devin can now manage a team of Devins.

Cognition

180K followers

Visit on X
416 likesDownloadOriginal post

111,653 views

Devin can now manage a team of Devins. Devin will break down large tasks and delegate them to parallel Devins that each run in their own VM. Over time, Devin gets better at breaking down and managing tasks for your codebase. Available now for all users.

21 Comments

Comments from the original post on X (Twitter)

  • Cognition's profile picture

    @cognition

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

    27 likes

  • Cognition's profile picture

    @cognition

    To learn more and view some sample prompts, check out our announcement here:

    22 likes

  • Jorge Zreik's profile picture

    @ZreikJorge

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

    8 likes

  • Devin's profile picture

    @DEVINSOLAI

    we called it.

    3 likes

  • samyok's profile picture

    @samyok

    can we call the orchestration agent kevin

    3 likes

  • Alex Kaplan's profile picture

    @alexkaplan0

    Very cool agent manager UI

    3 likes

  • Sandeep Shah's profile picture

    @sandeepDshah

    👀👀👀

    3 likes

  • Devin's profile picture

    @DEVINSOLAI

    one devin was already dangerous. now they coordinate.

    3 likes

  • Vivek's profile picture

    @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

  • Emad Ghorbaninia's profile picture

    @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

  • Ahmed Omar.'s profile picture

    @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

  • Joannot Fampionona's profile picture

    @JoannotFovea

    Can devin manage managers of devins?

    1 like

  • Venkat Raman's profile picture

    @venkat_systems

    shouldn’t kevin be managing devins?

    1 like

  • Bhargav's profile picture

    @codewithbhargav

    Devinception. Cool release though!

    1 like

  • AIPOCH's profile picture

    @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!

  • Jordan Schenck's profile picture

    @jordanschenck

    cursor ate ur lunch/launch

  • Utkarsh Singh's profile picture

    @Utkarsh51557661

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

  • Mingta Kaivo 明塔 开沃's profile picture

    @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's profile picture

    @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.

  • Ben Kraus's profile picture

    @BenKraus

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