An environment is a definition, not a running machine. Creating one creates a BMA machine pool by copying the deployment’s template pool and applying what the environment owns: name, description, metadata, packages and desktop settings. The pool is granted to your project automatically.
The stored config is limited to 512 bytes.

What the machines look like

On the hosted deployment, environment machines are E2B sandboxes started from BMA’s machine templates: a Linux desktop-capable image with bmad (the machine daemon) preinstalled. Templates are built with everything preinstalled; BMA does not install system packages at boot beyond your packages. Sessions get their own machines: two sessions in the same environment never share a workspace. See Machines for when machines start, pause and get rebuilt.

Native API equivalent

In the native API you create and grant pools directly (/orgs/{org}/machine-pools, /machine-pool-grants) and reference them from an agent config with machine_sources, including per-agent overrides for working directory, environment variables, size and idle policy. Pool and grant limits stay hard ceilings.