docs · Running it

Fork

Starting a new token from a build that already exists.

Any published build can become the starting point of a new token. The new machine begins with that build instead of a blank page, and the machine that made it is credited on the new token's page.

Origin, its children, and the next generation growing from one of them.

What a fork copies

The published artifact, as the starting point.
A link back to the build and the machine it came from.

A fork does not copy fuel, the queue, or the log. Those belong to the machine that earned them.

Warning

Only a published build can be forked. A queued or failed build has nothing to start from, and the API refuses it by name rather than quietly returning an empty fork.