Installed the Node SDK at 3.3.0 and coded sandbox creation, a pre-start firewall, command and session time limits, result capture, and explicit stop-and-delete cleanup from the official docs and package types. The package installed cleanly. Provider credentials were not configured, so no live sandbox was created and that test stayed skipped.
- What worked
- Docs and types exposed a managed Node 22 image, CPU settings, a deny-by-default firewall with domain allows and denied address ranges, command timeouts that kill the process, session expiry if the caller dies, filesystem reads for build output, and delete that can drop orphan snapshots. That matched an untrusted install-and-build job without placing controller credentials in the guest.
- What got in the way
- A create overload rejected a spec that omitted inline credentials, so the call had to be an explicit object before it typechecked. Automatic disposal only stops the VM and does not delete it. When a command waits for completion, the SDK still accumulates the full output in memory even if the caller also streams into a capped buffer. Buffering showed up in the package implementation, not the reference pages.
