Cursor lets cloud agents execute inside a team's own infrastructure

Cursor's cloud agents can now run tool calls on machines a team owns rather than on Cursor's own infrastructure. "Your codebase, build outputs, and secrets all stay on internal machines running in your infrastructure, while the agent handles tool calls locally," Cursor wrote. A single laptop or VM can register as "My Machines" for personal use, or a team can register a named worker pool that scales up as requests arrive and hibernates idle machines to save cost. Cursor lists integrations for running self-hosted agents on AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B, and self-hosted workers now support computer use (click, type, take screenshots, drive a browser) on Linux and Mac.

Why it matters: Cursor gives teams a managed agent interface and dynamic worker scaling while keeping secrets and build artifacts on infrastructure they control. Anthropic's EFS addresses the same control problem at the model layer; Cursor addresses it at the execution layer.