ComputeSDK

Open-source, provider-agnostic TypeScript SDK giving you one unified API over many code-execution sandbox providers (E2B, Modal, Daytona, Vercel, Cloudflare, CodeSandbox, Runloop, Tensorlake, …). "CloudFormation/Terraform, but for running other people's code." Source: computesdk.com/blog/announcement, 2026-06-15

What it is

One consistent API (compute.sandbox.* + compute.snapshot.*) to create sandboxes, run shell commands, work with filesystems, open ports, and snapshot state — without vendor-specific APIs. Source: docs.computesdk.com/getting-started/introduction, 2026-06-15

  • Provider packages under the @computesdk/<name> scope — install only what you need; swapping providers is usually a one-line change. 14+ providers: E2B, Modal, Daytona, Vercel, Cloudflare, CodeSandbox, Runloop, Tensorlake, Blaxel, Upstash, Namespace, Archil, HopX, plus just-bash (local, no auth).
  • Core computesdk package for multi-provider routing, round-robin load-balancing, and resilience; destroy/snapshot calls auto-route to the provider that owns each sandbox.
  • Filesystem CRUD, one-off + PTY/background command execution, port forwarding (getUrl({ port })), full TypeScript types, and custom-provider extensibility. Source: github.com/computesdk/computesdk, 2026-06-15

The pattern: unified provider abstraction

ComputeSDK is to sandboxes what the Vercel AI SDK / OpenRouter are to models — an abstraction layer that masks vendor APIs so you build once and hot-swap the backend. Source: computesdk.com/blog/announcement, 2026-06-15

Relevance to Agent Machines / Dedalus

ComputeSDK is effectively the open-source generalization of Agent Machines' substrate-routing axis: AM's MachineProvider adapters (E2B / Sprites / Dedalus / Vercel) are the same "one API over many sandbox providers" idea. The scopes differ — ComputeSDK unifies the sandbox layer only, while Agent Machines layers persistence, agent-runtime routing, the browser console, and fleet management on top ("more than a sandbox — a home"; see Persistent Sandbox Thesis). A @computesdk/dedalus provider would slot Dedalus Machines into the ComputeSDK ecosystem. It also collapses the Agent Sandboxes provider ecosystem into a single typed interface. Source: compiled, 2026-06-15


Timeline