When to use this profile
Use the Node profile for JavaScript scripts and repositories that depend on the npm ecosystem. Keep dependency installation separate from the agent's edit and test loop so a failing test can be distinguished from a missing package or registry outage. Return structured test results rather than feeding the model an unlimited terminal transcript.
Prepare a repeatable environment
- Pin the runtime and package manager and retain the repository lockfile.
- Install with the frozen-lockfile mode appropriate to the selected package manager.
- Inspect install scripts before running dependencies; package lifecycle scripts execute code.
pnpm --dir /work/project testReturn results the agent can use
- A test summary that separates assertions from setup failures.
- Generated JavaScript, TypeScript or JSON files.
- A patch limited to the task's working tree.
Use a repository with one passing and one failing test. Confirm the exit status, then deny registry access after installation and repeat the tests offline.
Resources and boundaries
Start with 2 vCPU and 4 GB of RAM, then measure peak memory and task duration on a representative fixture. These are workload planning values, not a benchmark or a provisioned configuration. Use the sandbox cost calculator to estimate running time and retained snapshots.
- Package installation can run untrusted lifecycle scripts; it belongs inside the isolated environment.
- Do not copy your workstation's npm credentials into the sandbox.
- Limit worker counts for test runners so they stay within the CPU and RAM allocation.
Keep model inference separate from this execution profile. A hosted model or gpuOS can decide the next action while the CPU environment runs it. The quickstart describes the account workflow and the proposed runtime contract.