Virtual machines

Choose File → New VM… (or the New VM… button in the Virtual Machines window). Only the name is required; the defaults are 2 CPUs, 2048 MB of memory and a 20 GB disk. The very first VM downloads the Debian base image (~3 GB) once — later VMs clone it and boot in seconds. VMs persist: stopping one keeps its disk, starting boots it again, deleting destroys the disk too.

A node without a hypervisor — a NAS, a container without /dev/kvm — runs the desktop without VMs: the list stays empty and says why, About This Computer shows the same reason, and everything else works as usual.

Right-click a running VM and choose btop to open its process monitor in an 80×24 terminal window. It runs the VM's installed btop over SSH; press q to quit and close the window. A failed launch leaves its error visible.

Double-click a VM in the list to open its window. The tabs:

• Services — TCP ports listening inside the VM, with one-click links, plus the routes already published to the web. Servers must bind 0.0.0.0 (not 127.0.0.1) to show up here or be exposable.
• Terminal — a full SSH terminal in the browser.
• Agent — tell the built-in coding agent what to build; it gets a shell in this VM and streams its work live.
• Expose — publish a VM port to an HTTPS subdomain (see below).
• Sessions — every chat pinned to this VM, agent runs included, each with a model-written one-line summary of what it accomplished; click one to reopen it in the Chat window.
• Notes — free-form notes about the VM, saved automatically. Agents are told to read these before working in an unfamiliar VM, so write down what runs where.