Managed agent development
Purpose: Launch a development host with the Node and agent versions you choose, a dedicated DreamLake machine identity, and discoverable DreamLake skills.
Scope: One EC2 machine, selected Codex/Claude tools and optional Codex daemon startup. Vendor login and a real remote development session are separate checks. The shared bootstrap manages identity and readiness; your project selects cloud resources and software. The executable folder is 18-managed-agent-dev. Copy the whole folder; it has no required sibling checkout.
Choose a provisioning path
The folder includes an independent Terraform recipe with reviewed plan/apply, Vault-backed recovery and exact-state cleanup. Alternatively, use an existing DreamLake EC2 provider configured with your region, image, machine/network/storage choices, Vault credential reference and protected bootstrap instance profile. Choose one path for a machine; running both creates two billable machines.
The managed path's agent.layer.json selects exact Node/Codex/Claude versions and
whether Codex starts at boot. Edit the file, omit unwanted harnesses, and use
dl providers preflight PROVIDER --file agent.layer.json --json before
launching. The canonical service-account guide
contains the supported schema, launch commands, security contract and rollback.
The matching backend release is required; an older backend rejects agentSetup.
Verify the result
Keep the exact instance, enrollment, request and run IDs. Require the enrollment online, the included hello job succeeded with exit code zero, selected harnesses and installed skills verified, and a permitted signed machine resource read. Reboot and repeat readiness before claiming persistence. A cloud launch or queued run receipt alone proves neither successful setup nor execution.
DreamLake machine identity does not supply vendor inference credentials. Complete vendor login through its existing protected flow, then execute a real development task before claiming that agent ready. Public fixture coverage verifies generated installation and readiness, not your chosen cloud image or vendor account.
Cleanup and recovery
After preserving work, terminate only the instance identified by this project's receipt and verify its final cloud state. Credential/account retirement is a separate operation. After an interrupted launch, retry the same request ID with identical input; changed software needs a new request. Terraform users follow this folder's saved-plan and Vault snapshot recovery procedures.