Executive Summary
Vercel has launched an update to its Sandboxes product, introducing automatic filesystem persistence by default. This feature automatically saves and restores the state of a development sandbox between sessions, removing the need for developers to manually manage snapshots. Sandboxes can now be created with durable, customizable names, allowing them to be easily retrieved and resumed from their most recent state, streamlining stateful development and testing workflows.
Key Takeaways
* Default Persistence: Filesystem state is now automatically saved and restored between sessions by default for all newly created sandboxes.
* Named & Resumable Sandboxes: Each sandbox can have a durable name, which is used to automatically resume its state from the last snapshot when a new session starts.
* Cost Management: The persistence feature consumes snapshot storage, which is billed separately. Developers can opt-out for ephemeral workloads (`persistent: false`) to minimize storage costs.
* New API Methods: The update includes new functions like `Sandbox.fork()` (clone a sandbox), `Sandbox.getOrCreate()` (idempotent retrieval), and `Sandbox.delete()` (permanent removal).
* Developer Experience Enhancements: Other improvements include richer metadata on `sandbox.stop()`, lifecycle hooks (`onCreate`, `onResume`), and custom tags for better organization and tracking.
* Availability: The feature is available immediately by updating to the latest versions of the SDK (`@vercel/sandbox@latest`) and CLI (`sandbox@latest`).
Strategic Importance
This update makes Vercel Sandboxes a more powerful tool for complex development workflows by abstracting away state management, improving developer productivity and enabling more sophisticated, stateful testing environments.