Image: Cursor
Why it mattersA team that could not use cloud agents because the code, build outputs, or secrets had to stay on its own network can now run the same agent workflow without moving any of that off internal infrastructure.
Cursor published a changelog entry on 2 September saying its cloud agents can now run on machines a team hosts itself. Cursor writes that the feature lets a team "keep tool execution entirely in your own network", with the codebase, build outputs, and secrets staying on internal machines while the agent handles tool calls locally.
Two ways to connect a machine
The release names two options. "My Machines" attaches a single laptop or virtual machine to a user account, for personal work. "Team pools" are named worker queues for a team or an enterprise, with autoscaling capacity that grows as demand grows and shrinks when workers disconnect. Pools also support hibernating idle machines and restoring them within a reconnect window, so a team is not paying to keep idle machines running.
Existing sandboxes are supported
Cursor lists a set of sandbox providers a self-hosted setup can send work to, so a team that already runs one does not have to add a new one. The named providers are AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B.
Computer use on Linux and Mac
Self-hosted workers also get computer use on Linux and Mac. Cursor describes it as agents being able to "click, type, take screenshots, and drive the browser", with the ability to watch the desktop and take control from inside Cursor. Until this entry, that class of automation was tied to Cursor's own environment.
This removes the problem that has kept many internal engineering teams from using hosted coding agents so far: the code and the secrets cannot leave the network, so the agent has to run where the code is. Cursor is now saying it will run its agent on a laptop, a VM, or a pool of machines a team already runs, and let the tool calls happen there. For anyone who has been running the local IDE only because the cloud version was not an option, that is the specific constraint that changes. The Cursor page does not name a plan or a price for the team pool version, and the changelog is the only source, so what remains to check before adoption is which subscription tier includes the pool feature and how billing works when a self-hosted pool autoscales.
Source
Primary source: Cursor changelog: Self-hosted machines.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
