1
Set up one machine
Create the machine that the copies are made from, and select the key’s Secret for it.Go to your repo’s folder on your computer. On this page, Push the folder to the machine. Because you give no destination, the folder lands in
Then install the dependencies in the machine, so that every copy already has them.
my-repo, npm ci, and npm test stand
for your own repo and its commands./data/home/my-repo.push copies your files without the .git folder. Start a git repository in the folder on the
machine, so that you can see later what each copy changed.2
Copy it
Copy the machine into three new machines. One command can make up to 5 copies.This command makes
try-1, try-2, and try-3 and waits until they run. Each copy has the
source’s disks, size, and Secret selection, and the source machine is not changed.3
Give each copy a prompt
Send a different approach to each copy. Each command prints the ID of the conversation that it started. To see whether an agent is still
working, list the conversations of its machine.You can also watch one agent work. This command follows its events until the turn ends.
agent prompt starts Claude Code as a background job in
the machine and returns, so the three agents work at the same time.4
Compare the results and keep one
When the agents are idle, look at what each copy changed and whether its tests pass. This command
does both in You can also copy a result to your computer to compare it there. This command copies the
try-2.dist
folder of try-2 to ./dist-b.5
Clean up
Delete the copies that you do not keep.
--yes skips the question that rm asks first.Run a script in each copy instead
A copy can run any command, not only an agent. To compare builds, benchmarks, or migrations, start a different script in each copy as a background job.Limits
- Each copy is a machine, so it counts toward your plan’s machines and machine starts a minute.
Before you raise
--count, see Fork many machines at once. - A paused machine cannot be forked, so resume it first. Limits on the Fork page lists the other cases.
- A fork copies a machine now. To start copies later, or more than 5 at a time, save a snapshot and create each machine from it.
Fork
What a copy gets from its source, and when a fork is refused.
Run a coding agent on your repo
Keys, prompts, and steering for one agent.