--- title: Four Gemini 4 Argon agents beat Minecraft in 27 hours,... description: A Google DeepMind paper describes four Gemini 4 Argon agents completing Minecraft end-to-end, defeating the Ender Dragon after 27 hours and 14 minutes with... canonical: https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Four Gemini 4 Argon agents beat Minecraft in 27 hours, per a Google DeepMind paper | daily.dev og:description: A Google DeepMind paper describes four Gemini 4 Argon agents completing Minecraft end-to-end, defeating the Ender Dragon after 27 hours and 14 minutes with... og:url: https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350 og:image: https://api.daily.dev/og/posts/EVt8pG350.png og:image:alt: Four Gemini 4 Argon agents beat Minecraft in 27 hours, per a Google DeepMind paper og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Four Gemini 4 Argon agents beat Minecraft in 27 hours, per a Google DeepMind paper **[Collections](https://daily.dev/sources/collections)** · 2 min read · 0 upvotes · 0 comments ## Summary A Google DeepMind paper describes four Gemini 4 Argon agents completing Minecraft end-to-end, defeating the Ender Dragon after 27 hours and 14 minutes with zero human intervention. Each agent controlled a player via the Mineflayer library, writing and debugging its own code, coordinating through in-game chat and shared memory. The agents wrote 2,783 programs and died 605 times while splitting tasks and recovering items for one another. Commentators highlight the significance of maintaining a single coherent plan across thousands of dependent steps over more than a day, calling it a more meaningful benchmark for long-horizon agent coordination than isolated clever tricks, and noting the paper itself was partly written with AI assistance. ## Content A new Google DeepMind paper on long-horizon multi-agent coding reports what its authors believe is the first end-to-end autonomous completion of Minecraft by AI agents. Four Gemini 4 Argon agents defeated the Ender Dragon in 27 hours and 14 minutes with no human intervention. ## How the run worked Each agent controlled one player through the standard Mineflayer library. Nobody assigned roles, wrote game logic, or scouted a seed in advance. The agents planned, wrote, and debugged every program themselves. They coordinated through in-game chat and a shared memory. Over the run they wrote 2,783 programs and died 605 times. They split up the work, shared what they learned, and recovered each other's items after deaths. ## Why it matters @omarsar0 points to the practical angle for anyone building agents for long software or enterprise tasks. The team had to keep one plan consistent across thousands of dependent steps for more than a day. That is the hard part, and it's a more useful test than any single clever step. @emollick calls the paper worth reading and easy to follow, partly because it was written with AI. He sees it as an accessible example of agents coordinating spontaneously toward a complicated goal, and of how their approach differs from the way humans would do it. ## Questions this post answers ### How long did it take AI agents to beat Minecraft autonomously using Gemini models? Four Gemini 4 Argon agents defeated the Ender Dragon in 27 hours and 14 minutes with no human intervention, according to a Google DeepMind paper on long-horizon multi-agent coding. Each agent controlled a player through the Mineflayer library, writing and debugging its own code, coordinating via in-game chat and shared memory, and together wrote 2,783 programs while dying 605 times. _daily.dev surfaces benchmarks like this for engineers evaluating long-horizon multi-agent coordination approaches._ ### What makes this Minecraft AI agent demo different from other agent benchmarks? No roles, game logic, or seed scouting were assigned in advance; four Gemini 4 Argon agents planned, coded, and debugged everything themselves while keeping one consistent plan across thousands of dependent steps over more than a day. Commentators note that maintaining long-horizon plan consistency is a harder and more practically relevant test than isolated single-step tricks. _Those building long-running coding agents can track such coordination benchmarks via daily.dev._ ## Community take How the wider developer community reacted, aggregated from 2 discussions and 164 comments across x (as of 2026-10-17). **TL;DR:** Discussion largely treats the long-horizon multi-agent coordination (shared memory, spontaneous role-splitting, recovery from 605 deaths) as the real story rather than the Minecraft win itself, though many question how much was genuine coordination versus brute-force retries on a forgiving, resettable task. **Sentiment:** 40% positive · 45% mixed · 15% skeptical **The case for** - Spontaneous division of labor without an assigned org chart or human-written roles is seen as a meaningful signal for multi-agent systems. - Recovering from 605 deaths while keeping a coherent shared plan over 27+ hours is viewed as a strong long-horizon coordination demo. - A reusable crafting fix propagating across all four agents is cited as a concrete example of real collaboration. **The pushback** - Minecraft's free respawn and 5-minute item-recovery window make this more a test of cheap retries/recovery than of flawless planning. - 605 deaths implies a very low success rate per attempt, which some read as fragile rather than genuinely robust. - Several ask whether the result reflects actual multi-agent coordination gains or is mostly one agent carrying the run / just brute compute. - Concerns that shared memory could propagate one agent's wrong belief to the whole team without an audit trail. **By community** - x (mixed): People are intrigued by the spontaneous coordination and death-recovery behavior but repeatedly question whether it reflects real planning versus cheap retries on a resettable game, and want more detail on shared memory, roles, and transfer to real-world tasks. **Hottest debate:** Whether the 605 deaths and recoveries demonstrate robust long-horizon coordination or mainly show that Minecraft's forgiving respawn mechanic lets brute-force retrying pass for teamwork. **Open questions** - How exactly did the agents divide roles — negotiated live in chat or emergent from the setup? - What was written into shared memory versus only kept in chat scrollback, and how were contradictions handled? - How would results differ on normal difficulty, with fewer/more agents, or with a single-agent baseline using the same token budget? - How did they distinguish a 'failed' action from an 'outcome unknown' one during recovery? - How much of the success came from the harness/tooling versus the underlying model's capability? **Highlights** > @omarsar0 605 deaths in 27 hours is one death every 11 minutes per agent. A Minecraft death costs a respawn and a 5-minute window to recover items, so this tests recovery under a free rollback more than one consistent plan. > — [eth\_sensei on x · 1 points](https://x.com/eth_sensei/status/2111100764126916793) > @emollick Part of what get’s lost with these examples of what an agent can do is the failure rate. These agents failed 605 times before completing the game 1 time - that’s a 0.17% success rate. Your agent will not do everything perfectly on the first run. You will need to give it > — [JohnBrueckner on x](https://x.com/JohnBrueckner/status/2111177706591138138) > @emollick The setup detail that stands out to me is that the only shared channel is the in-game chat, plus an Observer who reports but never plays. So any division of labor has to be negotiated in plain text. It would be interesting to see the same run with the chat removed. > — [DavidAgentic on x](https://x.com/DavidAgentic/status/2111174870579196354) > @emollick 605 deaths in 27h is the number i keep coming back to. respawn is free in minecraft, so the team can kinda brute force recovery. in a real repo a death is a bad migration or a force push to main, and nobody runs over to hand you your items back > — [chebyte on x](https://x.com/chebyte/status/2111177764959056346) > @emollick The crafting fix reused in 655 programs is the detail I like. One agent’s workaround became a tool all four kept reaching for. That’s a concrete collaboration artifact to inspect alongside the chat log. > — [liuzhao\_666 on x](https://x.com/liuzhao_666/status/2111171938941083929) **Source threads** - [x](https://x.com/omarsar0/status/2111093058024755365) · 0 points · 80 comments - [x](https://x.com/emollick/status/2111171225418408236) · 0 points · 84 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#google-gemini](https://daily.dev/tags/google-gemini), [#google-deepmind](https://daily.dev/tags/google-deepmind) [View this post on daily.dev](https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Four Gemini 4 Argon agents beat Minecraft in 27 hours, per a Google DeepMind paper","url":"https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350"},"datePublished":"2026-10-16T19:04:01.809Z","dateModified":"2026-10-17T01:50:10.253Z","description":"A Google DeepMind paper describes four Gemini 4 Argon agents completing Minecraft end-to-end, defeating the Ender Dragon after 27 hours and 14 minutes with...","image":"https://pbs.twimg.com/media/HUxirTnWUAAkZ3k.jpg","thumbnailUrl":"https://pbs.twimg.com/media/HUxirTnWUAAkZ3k.jpg","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,google-gemini,google-deepmind","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"Four Gemini 4 Argon agents beat Minecraft in 27 hours, per a Google DeepMind paper"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/four-gemini-4-argon-agents-beat-minecraft-in-27-hours-per-a-google-deepmind-paper-evt8pg350#faq","mainEntity":[{"@type":"Question","name":"How long did it take AI agents to beat Minecraft autonomously using Gemini models?","acceptedAnswer":{"@type":"Answer","text":"Four Gemini 4 Argon agents defeated the Ender Dragon in 27 hours and 14 minutes with no human intervention, according to a Google DeepMind paper on long-horizon multi-agent coding. Each agent controlled a player through the Mineflayer library, writing and debugging its own code, coordinating via in-game chat and shared memory, and together wrote 2,783 programs while dying 605 times. daily.dev surfaces benchmarks like this for engineers evaluating long-horizon multi-agent coordination approaches."}},{"@type":"Question","name":"What makes this Minecraft AI agent demo different from other agent benchmarks?","acceptedAnswer":{"@type":"Answer","text":"No roles, game logic, or seed scouting were assigned in advance; four Gemini 4 Argon agents planned, coded, and debugged everything themselves while keeping one consistent plan across thousands of dependent steps over more than a day. Commentators note that maintaining long-horizon plan consistency is a harder and more practically relevant test than isolated single-step tricks. Those building long-running coding agents can track such coordination benchmarks via daily.dev."}}]} ```