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 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
string
required
The source computer’s
instance_id: the value POST /computers returns as instance_id, and GET /computers/{id} as fly_instance_id. Unlike clone, fork does not take the UUID: a UUID returns 404.Response
Returns201 once the fork is running. The request has no body.
string
New computer UUID.
string
A generated name:
agent-1 (fork), then agent-1 (fork 2).string
Always
running: the response is sent after the fork has resumed.string
The fork’s
instance_id. Use it for the fork’s own calls, including another fork.Plan limits
A fork is a new computer, so it is charged against the workspace owner’s plan. It draws on their computer slot, account RAM, per-computer CPU/RAM ceiling, and the storage the source’s disk requires. Any of those being exhausted returns403. See https://orgo.ai/pricing.
Example
Response
Errors
Every error body carrieserror and code.
Authorizations
API key authentication. Get your key at orgo.ai/workspaces
Path Parameters
Source computer instance_id