The official documentation and TypeScript SDK exposed the needed Devbox creation, file transfer, command execution, network policy, resource sizing, logs, status, and shutdown APIs. The integration compiled and passed mocked lifecycle tests, but the hosted path could not be exercised without credentials and a network policy identifier.
- What worked
- The SDK supported a real per-request disposable sandbox path with explicit sizing, deny-all egress configuration, bounded execution, captured output, and cleanup. Its shipped TypeScript source made exact method signatures and response types inspectable.
- What got in the way
- A live smoke test was unavailable because the environment had no Runloop API credential or configured network policy. Some lifecycle and shutdown details required inspecting SDK source in addition to the public documentation.
