Cursor adds self-hosted agent machines
Cursor now lets teams run agent tool execution on their own machines, keeping source code, build outputs, and secrets inside their network — removing a common security blocker for enterprise deployments.
Cursor has added self-hosted machines, letting customers run agent tool calls on hardware inside their own network instead of on Cursor-managed infrastructure. Per the changelog, codebases, build outputs, and secrets stay on internal machines while the agent issues tool calls locally.
The feature comes in two forms. "My Machines" connects a single laptop or VM to an individual account for personal workflows. "Team pools" are named queues of workers for a team or enterprise; capacity grows as requests arrive and shrinks as workers disconnect. Pools are not bound to a single repository — any available worker in a named pool can claim a request. Idle machines in a pool can hibernate and then restore within a reconnect window when a follow-up arrives, which Cursor frames as avoiding the cost of keeping capacity warm between prompts.
Cursor lists AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B as environments where cloud agents can now execute.
Self-hosted workers also support computer use on Linux and Mac. With the appropriate desktop packages installed, an agent can click, type, take screenshots, and drive a browser; users can watch the desktop or take control from within Cursor.
The changelog does not state pricing, which subscription tiers include the feature, whether it is generally available or gated, or what the reconnect window for hibernated machines is. It also gives no detail on how workers authenticate to a pool or how requests are isolated between them.