Installed the JavaScript SDK at 3.3.0 and used it as the executor for a multi-command git checkout under a hard time cap. Official docs and the package type definitions described create-time CPU, memory, and session limits, a deny-by-default domain firewall, per-command timeouts, streamed logs, and explicit stop and delete cleanup. No provider credentials were available, so a live microVM was never created; the client failed closed on the controller.
- What worked
- The SDK installed on the first attempt. Create options covered vCPUs, memory, a session deadline, a domain firewall, and unpublished ports. Per-command timeout is enforced in the guest. The published universal image already includes Git and the language runtimes this plan needs. With credentials absent, the client failed closed and the plan stayed off the host.
- What got in the way
- A real microVM was never started, so startup, enforced quotas, artifact capture, and service-side cleanup were not observed. The public SDK reference was opened several times and still needed the installed declaration files to confirm validators, log fields, and credential variable names. Automatic disposal stops a non-persistent session and leaves the sandbox record, so cleanup has to call delete as well.
