Vercel Sandbox creation now returns a ready sandbox

Vercel Sandbox now resolves the Sandbox.create() promise only after snapshot restoration finishes, ensuring the sandbox is fully ready before any commands or file operations start. This eliminates the previous delay where the first operation had to wait for snapshot completion. The change means developers can run commands immediately after sandbox creation without additional latency. Startup errors now reject the Sandbox.create() promise directly, making debugging more straightforward by surfacing issues at creation time rather than during the first operation.

Snapshot restoration time is now counted as part of the sandbox creation process instead of the first operation, shifting the timing of when delays occur. This adjustment means the total time from sandbox creation to the first operation remains unchanged, but the distribution of that time has shifted. For uncached snapshots, the increase in creation time can be larger, while cached snapshots see a minimal impact of about 50 milliseconds at the 50th percentile. The change applies automatically without requiring any SDK upgrades or configuration adjustments.

The update to Vercel Sandbox creation behavior is designed to improve predictability and reduce unexpected delays during development workflows. By resolving the sandbox promise only after full readiness, developers gain clearer timing expectations for when their sandbox is operational. Error handling is also streamlined, as startup issues are now surfaced immediately rather than during the first operation. This adjustment aligns with Vercel’s goal of simplifying sandbox management for users.

No manual intervention is required to adopt the new sandbox creation behavior, as the change is applied automatically across all environments. Developers can refer to the updated Sandbox.create() documentation for technical details and implementation guidance. The modification primarily affects the timing and error handling of sandbox initialization, with no changes to the overall performance of the first operation. This ensures backward compatibility while improving the developer experience.