Summary
On September 3, 2026, Vercel added support for running Cursor Cloud Agents inside Vercel Sandbox. Each agent request executes in its own isolated Firecracker microVM, while Vercel Functions and Vercel Workflow act as a durable control plane that claims queued requests, provisions workers, monitors sessions, and cleans up automatically. Teams keep repository cloning, file edits, and command/test execution on infrastructure they control.
What changed
Vercel published a changelog entry and knowledge-base guide enabling Cursor's Self-Hosted Machines APIs (a Cursor Enterprise feature) to target Vercel Sandbox as the execution environment, using scale-to-zero workers, isolated microVMs, and durable orchestration.
Why it matters
It turns Vercel into a first-class execution substrate for a leading coding agent, letting enterprises run Cursor agents inside their own Vercel account for data-control and compliance reasons rather than on Cursor-hosted machines. The scale-to-zero, per-request microVM model also shows how agent execution is converging on the same serverless primitives used for web workloads.
Evidence excerpt
Cursor Cloud Agents can now run in Vercel Sandbox instead of Cursor's hosted machines. Vercel Sandbox provides an isolated Firecracker microVM for each agent request, while Vercel Functions and Vercel Workflow form a durable control plane that claims queued agent requests, provisions workers, monitors sessions, and cleans up automatically.