can now automatically save their filesystem state when stopped and restore it when resumed. This removes the need for manual snapshots, making it easier to run long-running, durable sandboxes that continue where you left off.Vercel Sandboxes A is the durable identity, now identified , its filesystem state, and configuration options. A is the compute tied to that state, invoked as needed.sandboxsessionby a name introduces orchestration that separates storage from compute, reducing the need for manual snapshotting, so:Automatic persistence Persistence is enabled by default in the beta SDK, can be disabled between sessions with .

When disabled, the sandbox still exists after being stopped and can be resumed by its name, but each session starts with a clean filesystem.persistent: false If a sandbox is stopped and you run a command, the SDK will transparently create a new session, so you don't need to check state or manually restart The beta SDK adds methods for managing sandboxes over their lifetime: The beta CLI adds configuration management and session inspection: This feature is in beta and requires upgrading to the beta and packages.SDKCLI Install the beta packages to try…