Windows · macOS · Linux guests
Create a guest, set up its native control utilities, validate readiness, and coordinate tasks across your VM lab. Machine Control covers the environment around the application as well as the application itself.
Tools inside the guest
Once provisioned, a guest's Machine Control utilities handle administration, apps, browser control, screenshots, and input inside that guest. Your agent can stay in its existing session and reach those tools through the configured transport.
Ordinary tasks can use the guest's running desktop without opening or focusing a hypervisor window, moving your host pointer, or typing into your own desktop. The VM's interactive session and native control services still need to be ready.
An agent inside the guest can call its resident utilities locally; an outside agent reaches the same control surface through an authenticated route. Running another agent inside the VM is optional.
Host-console observation and input are explicit tools for initial setup, diagnosis, and recovery. Ordinary application control uses the guest-side route.
From fresh guest to reusable environment
Platform tools support Windows image factories, Ubuntu installation, and prepared or fresh macOS images. Bootstrap guest administration and resident controls, then recheck each setup stage.
Read-only doctor checks report power, administration, session, and control readiness separately. Supported maintenance workflows audit runtime health, make explicit repairs, prove reboot recovery, and certify candidates.
Lifecycle and readiness guide →Exclusive, expiring claims reserve an exact VM for one task. Scoped runs perform readiness preflight, renew the reservation while work continues, and release it during cleanup.
Scoped task guide →Reuse a persistent development VM, run an isolated workspace and discard its changes, or retain a candidate for validation and promotion. The provider chooses the supported clone or overlay mechanism and handles owned-workspace cleanup.
Workspace guide →Releasing a reservation does not shut down a VM. Tasks arrange their intended power-state cleanup separately; isolated workspace cleanup follows its provider's retain/discard policy.
Choose the guest and its host
VM creation and coordination use the repository's CLI and platform tools. The desktop installer supplies control for an existing computer or guest; it does not create a VM by itself.
ARM64 under UTM on Mac, or native x64 under libvirt/KVM on Linux. Image factory, guest bootstrap, and candidate validation.
Windows factory guide →Tart on Apple hardware. Prepared images or fresh IPSW guests, native permissions, and guest readiness checks.
Mac bootstrap guide →Ubuntu under UTM on Mac or native x64 libvirt/KVM on Linux. Installation, guest tools, and resident setup.
Linux bootstrap guide →Host and guest support are separate. Windows-hosted VM routes remain experimental; factory and workspace qualification is still open. Seecontroller-host supportfor the current route coverage.