Story · Vercel
Cursor Cloud Agents can now run in Vercel Sandbox (Vercel)
blog post · Story page
Cursor keeps the agent harness and inference loop, and Vercel Sandbox supplies an isolated Firecracker microVM per agent request, with Vercel Functions and Workflow as the control plane that claims queued requests, provisions workers, monitors sessions, and cleans up. You get a scale-to-zero worker pool, durable retries, and short-lived user-scoped credentials, and Self-Hosted Machines requires a Cursor Enterprise plan.
In plain words
- Cursor's cloud coding system can now do its work inside isolated computers supplied by Vercel.
- Each request gets a separate short-lived virtual computer, keeping its files and commands apart from other work.
- Vercel's services assign queued requests, start workers, watch sessions, retry failures, and clean up afterward.
- Enterprise customers can run Cursor work in their own Vercel accounts without maintaining always-on worker computers.
Appeared in
- GPT-6 Astra's score hinges on its harness, and agents rot geometrically with each step
Sep 04, 2026 · in the sections
Subscribe
Get the brief in your inbox
Pick daily, weekly, or both. Nothing is gated either way: every issue is on the site and in the feeds.
- Weekdays at 8:45am IST, one lead story and 6 to 9 items.
- Sundays, an argued synthesis rather than a recap.
- One click to leave, and quiet days say so in the subject line.