Skip to main content
An IDYL Computer belongs to one Namespace and lives in one Subnet. Its name is unique within the Namespace and Subnet together. Its stable ID and durable state remain available independently of active execution. On the selected Subnet’s public API, Computer routes are nested under:
Direct Workload routes remain under the Namespace.

​
Settings and execution

spec.execution records the requested image, CPU, memory, connectivity, and environment variables. executionSettings reports the effective settings, including whether a change is pending. The separate execution field reports whether execution is dormant, waiting, or running. Saved state belongs to the Computer. The idle timeout can release execution without deleting that state. Use idyl computer edit to change settings and idyl computer history to inspect recorded execution-setting changes.

​
Lifecycle

Every Computer the API serves carries a phase:

​
Deleting a Computer

Deletion is asynchronous. IDYL records the Computer as terminating, releases what it owns, and finalizes the deletion. Once finalized, reads return 404 and its name can be reused within the same Namespace and Subnet. Deleting a Computer already terminating is accepted again. Deletion releases the Computer’s resources. Other Computers and direct Workloads in the Namespace remain available. Deleting the Namespace releases its Computers; see Namespaces.

​
While terminating

Automation should classify a refusal by its code. terminatingAt reports when deletion was recorded.

​
Observe and wait for deletion

--wait blocks until finalization. Use --timeout to bound the wait. After a deletion is accepted, the equivalent wait command is:
Both waits exit 0 when finalized and 124 when the timeout expires first.