Machines
A Machine is the configured execution environment for Agents in one factory. It records repositories, resources, capabilities, and optional environment and gateway settings. Agents name a Machine when they are created. The same Machine can serve Agents across Lines.
In the dashboard
- Open your factory (factories → choose one, or factory → Machines when using the default factory).
- Select New machine (or open an existing Machine to view builds and verification).
- Add the Git repositories the Agent needs, pick capabilities (Docker, SSH, browser-use), size, environment, and gateway options, then start a build at the level you need (
source,build, orverify). - Read the build and verification report on the Machine page. If a component fails, adjust configuration and rebuild before you assign the Machine to an Agent.
The dashboard walks component questions when a new Machine needs them. You do not need the CLI for day-to-day Machine creation.
Automate with the CLI
create starts the first build. Use --capability docker, --capability ssh, or --capability browser-use when the Agent needs those tools. You can also set CPU, memory, disk, environment, and gateway options. Inspect the Machine’s latest build and verification report before assigning it to an Agent. If a component fails, correct the Machine configuration and start another build:
The source, build, and verify levels control how far a build progresses. Verification reports component results and remediation. See the current options with islo factory machine create --help and islo factory machine build --help.
Assign and reuse
Set machine = "workbench" in an Agent config or pick the Machine in the Agent form. A Line refers to that Agent by name. Machine builds produce reusable versions; later runs use the Agent’s assigned Machine configuration. A Suggested Line can create missing Agents on a named Machine, or on the factory’s most recently created Machine. Prepare and verify the Machine before deploying a suggestion.
For runtime settings, see setup scripts, snapshots, gateways, and sandbox lifecycle.