Machines
Use this page for the full machine lifecycle: creation, connection, image selection, storage mode, sharing, and routine operations.
Create machines
Use a managed worker when you want the platform terminal, desktop, and agent runtime out of the box. Use a custom machine when you want to boot a specific OCI image and control the app process yourself.
In the dashboard, the new machine flow shows the image source that will be used, whether your filesystem default is isolated or shared, and an optional workspace name for the canonical /workspace-<workspace> path used by managed workers.
Connect to machines
Every machine has a primary app URL. Managed workers also expose a platform terminal, a platform desktop, and SSH access when enabled.
Use computer open for browser access instead of constructing reserved terminal or desktop URLs by hand. Use computer ssh to ssh into your machines
Images and filesystem
Managed workers use either the platform default image or your saved default machine source. Sources currently point at an OCI image. Only sources in ready state can become the default for new machines.
For storage, isolated mode gives each machine its own filesystem. Shared mode mounts a shared home at /home/node and starts agent sessions in /workspace-<workspace>, backed by /home/node/workspace-<workspace> when shared storage is enabled.
Monitor and update
Managed workers expose live CPU, memory, and disk metrics. They also show firmware versions and an update action when a newer managed image is available.
When a machine enters updating, Agent Computer rolls the runtime to the latest managed image and refreshes the machine when it is ready. Use the status badge and timestamps in the dashboard to confirm where the machine is in the lifecycle.