Skip to main content
Prepare one sandbox, fork it N times, and prompt each fork. Each agent gets its own disk, processes and IP address. They do not interfere. To run a few tasks on one sandbox instead, use parallel conversations. They share one disk and one desktop.

Watch the start limits

Each fork counts as one start. Above a limit, Boat refuses the fork with 429 rate_limited. The answer names the window that you hit.
  • An organization gets these limits times its number of seats.
  • Pace your forks below the per-minute limit. The examples below wait 6 seconds between forks, which fits the $20 plan.
Read Limits and errors for every limit and how to raise it.

1. Prepare the source sandbox

A fork copies the newest snapshot of its source. Stop the source first, so that its snapshot has your last change. A fork of a running sandbox can miss the writes of the last minute. The source needs your AI keys. Read Run a coding agent on your repo for the environment settings.

2. Fork N copies and prompt each one

  • --ttl 7200 gives each fork a 2-hour auto-stop. A fork never copies the auto-stop setting of its source. A running prompt moves the deadline by itself.
  • Idempotency-Key makes a retry safe. Without it, a retry after a lost answer can make a second fork that you pay for.
  • Prompts queue while a fork starts. You do not have to wait for ready before a prompt. The Python example waits only to fail early on a bad fork.

3. Collect the results and clean up

Each <id>.log file holds the work of one agent. Then read the result in each fork and stop or delete it:
A fork that you do not stop stops by itself at its auto-stop deadline.