Supported platforms
Linux and macOS run natively. There is no Windows build; a Windows estate runs the product on Linux underneath.
There are two things to place on a platform, and they are placed separately: the server — the control plane that holds the record and drives the work — and the agent machines the server dispatches onto.
| platform | the server | agent machines |
|---|---|---|
| Linux (x86-64, ARM64) | natively | natively, as container images, or as Linux virtual machines |
| macOS (Apple silicon) | natively | natively, or as Linux containers and virtual machines |
| Windows | ⚠ only on Linux underneath — see below | Linux, virtualized — container images or Linux virtual machines |
The release targets are darwin-arm64, linux-amd64 and linux-arm64; there is no
darwin-amd64 and no Windows build.
⇒ Container images are a form of agent machine on every platform, not a Windows workaround, and the product ships a template per language class. See Agent machines. ⚠ A container run is placed on the local machine only; a container run on a remote machine is refused in this release (Sandboxing).
Windows
⚠ There is no native Windows build of either half. What a Windows estate can do is run the product on Linux underneath: the server in a Linux virtual machine or container, and each agent machine as a Linux container or a Linux virtual machine. Everything above that layer is identical to a Linux install: the same streams, the same roles and seats, the same gates, the same record.
⚠ State: not proven. No server container image is published, and this shape has not been exercised end to end on a Windows host. What is therefore not proven is the whole Windows deployment, including how the console and its passkey prompt behave when the browser runs on Windows and the server in a virtual machine. On Windows, a container runtime or a hypervisor is part of the installation rather than an optional convenience — see Deployment.
Why virtualized rather than native
The controls this product places around an agent session — what it may write, what it may reach — rest on the confinement facilities that Linux and macOS provide, and each is measured per platform rather than assumed. ⇒ Running agents on Linux, virtualized, gives a Windows estate the same boundary as a Linux estate, described by the same pages. A native Windows build would need its own confinement story before any of it could be stated in writing.
See Sandboxing for what confinement each platform offers.
Agent machines can be a mix
The server's platform does not constrain the machines it drives, and neither does their form. A fleet can run host machines, container images and virtual machines at once — Linux beside macOS — each in its own seat, under the same streams, the same gates and the same ledger. ⚠ What differs per machine is the confinement available to a session there, which is measured on the machine rather than inferred from its platform.