Resize computer
Change CPU, RAM, disk, bandwidth, or auto-stop on a running computer.
running. The response reports the values the computer actually accepted, not the ones you asked for: a dimension that failed to apply comes back with its previous value.
Path parameters
instance_id. Both resolve to the same computer.Body parameters
0.5, 1, 2, 4, 8, or 16, as a JSON number. Any other value returns 400. A value above your per-computer ceiling returns 403. Omitted leaves CPU alone.4, 8, 16, or 32, as a JSON number. Any other value returns 400. A resize tops out at the host’s boot-memory ceiling, 32 GB by default, whatever your plan allows. 64 is accepted only on a fleet configured above that ceiling; otherwise a 64 GB computer is only reachable at create time. A value above your per-computer ceiling returns 403. Omitted leaves RAM alone.400. A value below 1 or above this computer’s ceiling also returns 400, with max_disk_gb in the body. Omitted leaves the disk alone. Call GET /computers/{id}/resize to read the ceiling first.400. 0 is accepted but leaves the cap unchanged. Omitted leaves the cap alone.0 means always-on. Omitted leaves the current setting alone. This is applied separately from the four hardware dimensions and is not reflected in results. Orgo does not check the value before resizing: a value the host rejects, such as a negative number or more than 43200 (30 days), returns 500 after any hardware change has already applied.Response
Returns the effective configuration after the resize attempt.auto_stop_minutes you sent, echoed back. Absent when you did not send it.true when the computer’s ports or VNC password changed. Re-fetch the computer’s connection details before reconnecting.true when the resize restarted the computer, false when it applied live. null when the host does not report it.api_port, novnc_port, vnc_password, ssh_host_port, or ip. Empty when nothing changed or the host does not report changes.{ "dimension": "vcpus" | "mem_mb" | "disk_gb" | "bandwidth_mbps", "requested": number, "applied": number, "ok": boolean, "error"?: string }. This is an array, not an object keyed by dimension. Iterate it and switch on dimension. A dimension sent at its current value has no entry. Absent when the request included no hardware dimension.true when at least one dimension failed, false otherwise. It is true on both 207 and 422, so use the HTTP status to tell a mixed result from a total failure. Absent when the request included no hardware dimension.Status codes
200: every requested dimension applied207: some dimensions applied and others failed (checkresults)422: every requested dimension failed
Example
Response
Errors
Read the ceilings before resizing
GET /computers/{id}/resize returns this computer’s headroom, so you can size a request before making it. It takes the same path parameter and no body.
disk_size_gb this computer can be resized to. It is the plan’s base plus whatever add-on storage the owner’s other computers have not already claimed, up to 300 GB.mem_gb this computer can be resized to, already bounded by the live-resize limit and by the RAM the owner’s other computers leave in the account’s pool.vcpus this computer can be resized to.bandwidth_limit_mbps the workspace owner’s plan allows.true when a mem_gb change applies without restarting the computer. Absent when the host cannot say, for example when the computer is not running.200 with a different shape: resizable: false, reason, code, and current_disk_gb, max_disk_gb, max_ram_gb, and max_cpu all set to its current size.
Authorizations
API key authentication. Get your key at orgo.ai/workspaces
Path Parameters
Computer ID
Body
New vCPU count. Omitted, the CPU is left alone. Capped by the workspace owner's plan; call GET /computers/{id}/resize for the ceiling.
0.5, 1, 2, 4, 8, 16 New RAM in GB. Omitted, the RAM is left alone. A resize tops out at the host's boot-memory ceiling, 32 GB by default, whatever your plan allows: 64 returns 400 unless the fleet is configured above that ceiling, so a 64 GB computer is otherwise reachable only at create time. Above your per-computer ceiling, or more than your other computers leave in the account's RAM pool, returns 403. Call GET /computers/{id}/resize for the ceiling.
4, 8, 16, 32 New disk size in GB. Omitted, the disk is left alone. Grow only: a smaller value returns 400. Below 1 or above this computer's ceiling also returns 400, with max_disk_gb.
New bandwidth cap in Mbps. Omitted, the cap is left alone. Must be non-negative and no higher than the owner's plan limit; either violation returns 400.
Idle minutes before the computer suspends itself. 0 means always-on. Omitted, the setting is left alone. Applied separately from the hardware dimensions and not reflected in results. Orgo does not check the value first: a value the host rejects, such as a negative number or more than 43200 (30 days), returns 500 after any hardware change has already applied.
Response
Every requested dimension applied
The effective configuration after the resize attempt. A dimension that failed to apply comes back with its previous value.
Effective vCPU count.
Effective RAM in GB.
Effective disk size in GB.
Effective bandwidth limit in Mbps.
The auto_stop_minutes you sent, echoed back. Absent when you did not send it.
true when the computer's ports or VNC password changed. Re-fetch GET /computers/{id} before reconnecting.
true when the resize restarted the computer, false when it applied live, null when the host does not report it.
Connection values the host reports as changed. Empty when nothing changed or the host does not report changes.
api_port, novnc_port, vnc_password, ssh_host_port, ip One entry per attempted hardware dimension. Absent when the request included no hardware dimension.
true when at least one dimension failed. true on both 207 and 422. Absent when the request included no hardware dimension.