VercelEngineering PostOfficial Source

Cursor Cloud Agents can now run in Vercel Sandbox

Cursor Cloud Agents can execute inside per-request Vercel microVMs, giving teams control over isolation, credentials, retries, and worker lifecycle without operating persistent VMs.

Vercel · Sep 3, 2026

Open Source Open Markdown Open JSON

Source Summary

Cursor now lets Cloud Agents run on **Vercel Sandbox** through its Self-Hosted Machines APIs. Cursor retains the harness and inference loop, while each request gets an isolated **Firecracker microVM**; Vercel Functions and Workflow handle queues, provisioning, monitoring, retries, and cleanup.

Practical Implication

This separates agent orchestration from execution infrastructure. Teams needing tighter runtime control can use scale-to-zero workers and short-lived, user-scoped credentials instead of maintaining a standing VM pool.

Agent-Ready Context

Cursor now lets Cloud Agents run on **Vercel Sandbox** through its Self-Hosted Machines APIs. Cursor retains the harness and inference loop, while each request gets an isolated **Firecracker microVM**; Vercel Functions and Workflow handle queues, provisioning, monitoring, retries, and cleanup.

This separates agent orchestration from execution infrastructure. Teams needing tighter runtime control can use scale-to-zero workers and short-lived, user-scoped credentials instead of maintaining a standing VM pool.

Self-Hosted Machines requires a **Cursor Enterprise** plan, and the source describes a reference implementation rather than its operating cost or performance under load.

Connected Context · Feed7 Judgment

This makes the brain-versus-hands split deployable for Cursor: Cursor keeps orchestration while Vercel supplies isolated, per-request execution and lifecycle machinery. It reduces the need for a standing worker fleet and supports user-scoped credentials, but narrows access to Enterprise customers and leaves cost, capacity, and load behavior to be validated.

Scaling Managed Agents: Decoupling the brain from the handsThe reference implementation concretely applies Anthropic’s stateless-brain and replaceable-sandbox architecture to Cursor, with Vercel handling provisioning, retries, and cleanup.Tethered: Our Agents Are Us — Shu Fang, Two SigmaIts short-lived, user-scoped credentials reinforce Two Sigma’s principle that remote agents should retain employee attribution instead of operating through undifferentiated agent identities.Give every agent in Herdr its own Vercel SandboxBoth use separate Vercel sandboxes to prevent agent execution from sharing a local environment; Herdr adds reviewable Git patches, while Cursor’s design emphasizes managed request lifecycle.Vercel AI Gateway and Vercel Sandbox now available on Hermes AgentBoth show that the agent harness and its execution environment can be selected independently, with sandbox adoption requiring explicit infrastructure configuration.

Context Map

infracodingsecurity#cloud-agents#sandboxing#coding-agents

Uncertainty

Self-Hosted Machines requires a **Cursor Enterprise** plan, and the source describes a reference implementation rather than its operating cost or performance under load.