Computers
Fork computer
Copy a running computer, memory included, so the copy carries on from the same moment.
POST
Fork computer
Creates a copy of a running Linux computer, including what is in its memory. The fork comes up
running in the source’s workspace, or in another workspace you own when you send workspace_id, with the same apps, windows, and processes open, so an agent can carry on from the exact same point.
Clone or fork?
Clone a computer to reuse its setup. Fork it to try two next steps from the same moment.
The source pauses for about two seconds while its memory is copied, then carries on. The fork gets a new UUID and a new
instance_id. Its auto-stop is forced to always-on regardless of the source’s setting.Path parameters
The source computer’s UUID or
instance_id. Both resolve to the same computer, as on the other computer endpoints.Optional body
The workspace the fork lands in. Omit it, or send the source’s own workspace, to fork in place. Another workspace must be one you own, and you must also own the source’s workspace; otherwise the request returns
403 with code WORKSPACE_ACCESS_DENIED. The plan checks then run against that workspace. A body that is not JSON is ignored, and the fork lands in the source’s workspace.Response
Returns201 once the fork is running.
Identifier of the fork’s current VM. It changes when the computer is started from its archive or wakes from storage, so keep
id (the UUID) as your handle and read this fresh from Get computer.Plan limits
A fork is a new computer, so it is charged against the workspace owner’s plan. It draws on their computer count, account RAM, per-computer CPU/RAM ceiling, and the storage the source’s disk requires. Any of those being exhausted returns403. See pricing.
Example
Response
Errors
Every error body carrieserror and code.