We placed four Gemini 4 Argon agents in a sandboxed Minecraft survival world and gave them one goal: defeat the Ender Dragon. Each agent controlled a player via an open-source library called Mineflayer and coordinated with its teammates through in-game chat and shared memory. No one assigned roles or wrote game logic. The agents planned, wrote, and debugged every program themselves. Researchers could watch the run on a live dashboard and pause or stop it at any time, but they had no cause to intervene. Starting from a randomly generated world on Easy difficulty, the team wrote 2,783 programs and defeated the dragon in 27 hours and 14 minutes, dying 605 times along the way. To our knowledge, this is the first end-to-end autonomous completion of Minecraft by AI agents, achieved using only the standard Mineflayer library without pre-scouted seeds or other game-specific tools written by humans. Winning required the agents to keep a coherent plan across thousands of dependent steps for more than a day. Complex real-world software engineering and enterprise tasks demand the same long-horizon coding and multi-agent coordination. We describe the setup, how the run unfolded, the team's strategies (dividing the work, sharing what they learned, recovering each other's items), and the limits of the result.
Figures & tables
Figure 1: The four agents, and their run step by step: the thirteen steps from bare hands to the Ender Dragon, each colored by the player who reached it first, over 27 hours and 14 minutes. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 2: How each agent plays. It writes a JavaScript program, a Mineflayer bot runs it in the shared world, and text comes back. The players share the game’s chat and can read each other’s notes. A fifth agent, the Observer, reports on the game but never plays. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 3: The whole run. Each lane is a player: dots are chat messages, diamonds are advancements, red ticks are deaths. Bars count programs per half hour; orange dashes mark the six restarts of the world server. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 4: The thirteen dependent steps from initial spawn to the Ender Dragon, each with the time the team first reached it and the player who did. Item icons from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 5: Chat in the first quarter hour: janesick proposes roles ten minutes in, and auratian answers with a different plan within a minute. Messages in all chat figures are verbatim, timed from the first program; […] marks an elision. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 6
Figure 6: After a Ghast fireball destroyed dropped items, auratian posts a rule for the team, and janesick follows two minutes later with the root cause and a fix. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 8
Figure 7: janesick’s two throws, minutes apart in the eleventh hour of the run, and where the lines cross. Coordinates are in blocks; one block is one meter. Item icons from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 8: auratian drowns carrying all twelve Eyes of Ender. janesick and auratian send bulicame the exact spot and the despawn deadline, and bulicame recovers all twelve. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 9: The End portal in the stronghold, with all twelve eyes in place. Rendered with the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 10: Rules for the End, written between attempts at the dragon: never wait on the arrival platform, leave the End to reset a stuck dragon, approach only while it perches. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 11: auratian finds why the dragon stays at full health, the healing crystals, and then a way to reach them without a pickaxe. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 12: Left: the ten crystals on the End island, seen from above, colored by the player who destroyed each, with the time into the run. Right: the dragon’s health in the final fight, as the players’ own programs read it. Item icons from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.
Figure 15
Figure 13: Left: messages that match simple patterns for each behavior, by sender; a message can match several. Right: the 605 deaths before the win, by cause, from the server log.
Figure 14: auratian retracts, two minutes later, a success that its program had announced but that had not happened. Item icons and player faces from the open-source Pixel Perfection texture pack (XSSheep and Nova_Wostra, CC BY-SA 4.0), not Minecraft’s textures.