Summary
Vercel made sandbox persistence generally available, so Sandboxes now save and restore filesystem state automatically between sessions. Persistence is on by default and can be paired with named sandboxes, get-or-create flows, and automatic resume behavior.
What changed
Sandbox persistence moved to GA, making automatic filesystem snapshots and resume behavior the default for Vercel Sandboxes, with new lifecycle hooks and management methods around that model.
Why it matters
Durable execution environments matter more as agent and coding workflows shift from single prompts to long-running tasks. Vercel is turning sandbox statefulness into a default primitive, which lowers the friction for agent loops, preview environments, and resumable dev tasks.
Evidence excerpt
Vercel says Sandboxes now automatically save and restore filesystem state between sessions, with persistence enabled by default and automatic resume from the latest snapshot.