zeo5 fork arena

+00:00.000run
connecting
lineage · one host wake, the rest fork themselves · click a box for its console

one VM wakes.
the agent forks itself to solve a maze.

Git-like branching for live virtual machines: a VM forks in milliseconds, each branch holds only what it changed, and the whole lineage is a tree you can wake, diff, compact or throw away.

One prompt starts it. The agent in the first VM writes up to three maze-solving strategies, forks itself once into three solver VMs, watches them race through the same maze on their own consoles, declares the first to the exit the winner, and that winner takes over the conversation and forks the next round.

VMs alive
0
of 6 warm slots
woken by the host
0
forked from inside: 0
last wake to ready
—
load + resume, measured by the VMM
memory per clone
—
PSS, shared pages counted once
fastest solve
—
first to the exit wins
“The host woke one VM. Everything else is the agent deciding to exist twice.”

the one prompt that starts everything

This is the system prompt the agent in the first VM wakes up with. Edit it if you like: placeholders {rounds}, {seconds}, {max_solvers}, {problem}, {contract} are filled in by the agent. After the first message below, nobody intervenes: the agent writes the strategies, forks, judges, and the winner carries the conversation on.

zeo5 in one screen

Git-like branching for live virtual machines: a VM forks in milliseconds, each branch holds only what it changed, and the whole lineage is a tree you can wake, diff, compact or throw away.

click outside to close

workspaces

close ✕
$