Cursor Cloud Agents can now run in Vercel Sandbox
Cursor Cloud Agents can now run in Vercel Sandbox instead of Cursor's hosted machines. Cursor manages the agent harness and inference loop.
Cursor Cloud Agents can now execute inside Vercel Sandbox instead of Cursor's own hosted machines. Cursor still manages the agent harness and inference loop, but its Self-Hosted Machines APIs (which require a Cursor Enterprise plan) can now point at Vercel Sandbox as the execution environment where agents clone repositories, edit files, and run commands and tests. Each agent request gets its own isolated Firecracker microVM, with Vercel Functions and Vercel Workflow acting as a durable control plane that claims queued requests, provisions workers, monitors sessions, and cleans up automatically.
This setup provides:
- A scale-to-zero worker pool without long-lived virtual machines
- A dedicated, isolated Sandbox for every agent request
- Durable retries when a worker or session fails
- Short-lived, user-scoped credentials inside each Sandbox
Vercel has published a step-by-step guide for deploying the reference implementation to a Vercel account.
