Cursor adds self-hosted machines that keep tool execution inside your network
Original titleSelf-hosted machines
AISummary
Cursor now supports self-hosted machines, so tool execution stays on your own infrastructure while the agent makes tool calls locally.
Team pools are named worker queues that scale with requests and can hibernate idle machines, restoring them within a reconnect window.
Cloud agents can also run on sandboxes such as AWS Lambda, Cloudflare, Modal, and Vercel, and self-hosted workers now support computer use on Linux and Mac.
AIWhy it matters
The update explains how self-hosted workers keep tool execution inside your network while pools scale and hibernate, which matters for teams with strict data controls.
Source: Cursor Changelog · cursor.comPublished · added here