Run a 50-agent civilization in survival Minecraft and watch it self-organise

YC Labs and Olam Labs put 50 GPT-6.1 Sol agents in a survival Minecraft world for 3 hours; they sent about 5,900 messages, died 34 times and ended up running a food ration office.

Done withCustom agent· Undated · 2 accounts

What they did

Y Combinator's labs team, working with Olam Labs, wanted to study how swarms of agents coordinate. No harness for long-running Minecraft agents existed, so they built one and open-sourced it: the core loop runs on Pi, and the agents act through tools built on Mineflayer's scripting layer. Each agent could observe the world, keep memory, write and run scripts and send direct messages. In the run they call Civ50, 50 agents on GPT-6.1 Sol got one goal, build a thriving civilization, plus an agent directory and a shared sandbox machine for notes, and were left alone in a survival world for three hours.

How it went

The agents cleared almost every tree near spawn in about 90 seconds. The first agent in the directory, Ada, became the leader by default and wrote the colony plan into shared files. The first night killed 22 agents (34 deaths over the run), after which the group turned cautious, dropped building and scouting, and spent most of the run in shelters. One agent kept a food queue file and approved rations by message, catching misdelivered food and stale reports. In all they sent about 5,900 messages. The write-up also covers a second set of runs in Mindustry.

Worth knowing

Dying cost the agents nothing but their gear, yet they still became very risk-averse. An HN commenter found their play slow and almost turn-based, even in a Bed Wars mode that should have rewarded speed. Fifty agents sharing scarce food turned the goal into survival logistics rather than building.

Try it

With Custom agent· 7 parts to fill in

You are one of [number] agents in a shared [survival game world] with one goal: [build a thriving settlement]. You can act through [the game scripting tools], message other agents by name from [the agent directory], and read and write files on [a shared machine]. Keep a plan file and a resource ledger there, record who holds what and who needs what, and confirm every handoff with the recipient before marking it done. Avoid tasks that risk dying unless the plan needs them. Stop after [hours] and write a summary of what the group built, how many messages were sent and how many agents died.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related