Cursor Cloud Agents Now Run on Self-Hosted Infrastructure

Cursor officially announced that cloud agents can now run on users' own infrastructure, including machine pools that auto-scale on demand. One user has already demonstrated running a Cursor cloud agent on a Mac Mini.\nConfirmed\n- Cursor launched Self-Hosted Machines: Cloud Agents can perform file, terminal, browser and local MCP operations on enterprise-owned machines, while the agent loop, model inference and session management remain in Cursor's cloud — a "cloud reasoning + local execution" architecture\n- Supported sandbox providers include AWS Lambda, Coder, Cloudflare, Daytona, E2B, Modal, Namespace and Vercel\n- Self-hosted machine pools can be built on Cloudflare Containers, letting agents integrate with the user's Cloudflare ecosystem\n- Benefits include access to internal services, private APIs or dedicated hardware (e.g. GPUs) while retaining elastic scaling\n- Per @dinasaur404, over 60% of internal PRs at Cursor are already created by agents\nWhy it matters\n- Previously cloud agents could only run in Cursor-managed sandboxes, leaving internal services and proprietary data out of reach; self-hosting extends cloud agents to compliance-, security- and hardware-sensitive scenarios\n- The split of "loop in the cloud, execution on-prem" keeps Cursor in control of agent behavior while handing the execution surface to users\n- Broad sandbox provider support gives enterprises flexible integration with existing infrastructure

2026-09-03 ~ 2026-09-03 · 6 related posts

Primary sources

1 near-duplicate retellings: ritakozlov