Cursor ships Self-Hosted Machines so cloud agents run tool calls on customer infrastructure

On September 2 Cursor's official blog shipped Self-Hosted Machines. The feature moves tool execution for Cursor cloud agents from Cursor-hosted infrastructure to machines that customers control, while leaving inference and planning in the Cursor cloud. Tool outputs flow back to Cursor for the next inference round, and customer code, build artifacts and secrets never leave the customer's network. To register a machine, the customer installs the Cursor CLI and runs agent worker start, which opens a long-lived outbound HTTPS connection to the Cursor cloud. No inbound ports, public IPs or VPN tunnels are required.

Two deployment modes are supported. My Machines connects a single laptop or VM to a personal account, suited to personal workflows. Pools are named queues of workers that can serve a team or enterprise, scaling up as demand arrives and shrinking as workers disconnect. Cursor provides Helm charts and a Kubernetes Operator for enterprise worker pool lifecycle management. Pools are not bound to specific repositories; a request only needs to identify the pool, so a single pool can serve many repositories. A new hibernation feature snapshots idle machines when an idle timeout expires and restores them with the same worker ID if a follow-up task arrives within the reconnect window, otherwise reassigning the request to a new machine.

Supported out-of-the-box sandbox providers are AWS Lambda, Coder, Cloudflare, Daytona, E2B, Modal, Namespace and Vercel. Cloudflare published coordinated press material on the same day noting that its sandboxes are now available as a worker target, simplifying setup for teams already running on Cloudflare Workers. Linux and Mac workers both support Computer Use, letting agents screenshot, click, type and drive a browser on the worker machine. Users can watch the agent's desktop or take control directly from Cursor, with typical use cases including frontend testing and UI automation. Cursor published a decision guide alongside the launch: use Cursor-hosted cloud agents where external tool execution is acceptable, and switch to Self-Hosted Machines where compliance requirements, internal tooling access or Computer Use on customer machines is needed.