Self-hosted machines

Summary

Cursor’s self-hosted machines keep tool execution inside an organization’s own network, leaving the codebase, build outputs, and secrets on internal infrastructure while the agent handles tool calls locally. The feature supports My Machines for connecting one laptop or VM and team pools that provide named queues of workers, with capacity expanding as requests arrive and contracting when workers disconnect. Pools are repository-independent, can hibernate idle machines, and can restore them within a reconnect window, avoiding the need to keep costly capacity warm. Cloud agents can run on infrastructure including AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B, while Linux and Mac workers add computer use for clicking, typing, screenshots, and browser control.

Takeaways

1. 1

   My Machines connects one laptop or VM for personal workflows, while team pools provide named queues of workers for teams or enterprises.

2. 2

   Pools are not tied to a repository and can hibernate idle machines, restoring them within a reconnect window instead of keeping expensive capacity warm.

3. 3

   Linux and Mac self-hosted workers support computer use, including clicks, typing, screenshots, browser control, desktop viewing, and manual takeover.

FAQ