Cursor Cloud Agents now run in Vercel Sandbox
Cursor Cloud Agents can now execute in Vercel Sandbox instead of Cursor's hosted machines, leveraging Vercel Functions and Vercel Workflow to provide isolated Firecracker microVMs per agent request with automatic provisioning, monitoring, and cleanup.
can now run in instead of Cursor's hosted machines. Cursor Cloud AgentsVercel Sandbox
Cursor manages the agent harness and inference loop. Its APIs let you supply the execution environment where agents clone repositories, edit files, and run commands and tests. Self-Hosted Machines requires a Cursor Enterprise plan.Self-Hosted Machines
Vercel Sandbox provides that execution environment as an isolated Firecracker microVM for each agent request. and form a durable control plane that claims queued agent requests, provisions workers, monitors sessions, and cleans up automatically.Vercel FunctionsVercel Workflow
With this architecture, you get:
Follow the to deploy the reference implementation to your own Vercel account, or learn more in the .step-by-step guideVercel Sandbox documentation
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
Source: original entry ↗