Computers
Clone computer
Duplicate a computer, preserving its disk state.
POST
Clone computer
Creates a copy of an existing computer with the same disk state, using your optional
Cloning is a disk copy, so stop applications that require an application-consistent backup before cloning. Guest flush and snapshot consistency depend on the computer backend.
name, or a generated (clone) suffix. The clone lands in the source’s workspace, or in another workspace you own when you send workspace_id, and comes up running.
Cloning copies the full disk: installed software, files, browser sessions. The clone gets a new UUID and a new
instance_id. Its auto-stop is forced to always-on regardless of the source’s setting.Clone or fork?
Clone a computer to reuse its setup. Fork it to try two next steps from the same moment.
A computer you stopped is
frozen: its disk is archived and no host has a VM to copy, so clone returns 400 with code NOT_CLONABLE. Start it, then clone it.
Path parameters
The source computer’s UUID or
instance_id. Both resolve to the same computer, as on the other computer endpoints. The instance_id is the value POST /computers returns as instance_id, and GET /computers/{id} as fly_instance_id.Response
Returns201 with the clone’s identifiers.
Identifier of the clone’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 clone 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.
Optional body
A name of 1-255 characters after trimming, unique in the workspace the clone lands in. Omit it to generate a name. An empty or invalid name returns
400 with code INVALID_REQUEST; a name collision returns 409 with code NAME_TAKEN.The workspace the clone lands in. Omit it, or send the source’s own workspace, to clone 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.Authorizations
Body
application/json