Capabilities

Project preparation and execution environment mechanisms.

Specification

Mechanism	Implementation
Warm nodes	A pre-provisioned node removes machine provisioning from task startup. With prewarming enabled and an available warm node, work can start in seconds. A warm node is unused capacity; after its operation it is deleted, not returned to the pool.
SOCI and internal container registry	AWE environment images are published with SOCI indexes to the internal registry. Lazy loading lets the worker start before the entire image is downloaded; remaining image data is fetched in the background.
Prepared project environment	The AWE contains project runtimes, dependencies, tools, service configuration and execution instructions for running the application and its checks.
Separate rootless Docker daemon	Docker runs on the node outside the agent container, without Docker-in-Docker inside the worker. The daemon supports image builds and containers for project services such as databases and queues. The daemon belongs to the worker stack on its single-use node; it is not shared across customer tasks.
Project service images	The environment declares service images in prewarm_images and Dockerfile builds in source_builds. The current runtime pulls or builds these images on demand; proactive prewarming is not active.
Cache reuse and refresh	Prepared dependencies and generated artifacts are reused. Refresh updates or invalidates them for the selected source revision. Reuse applies to caches stored in the project image, not the mutable workspace of a completed task.
Application verification	Builds, unit and integration tests run in the prepared environment. Headless Playwright checks are available when the project provides the browser and its dependencies.
Optimized agent harness	A harness tuned for AWE execution, focused on shorter task runtimes and lower token usage.