Run cloud agents on machines you manage

Cursor has introduced Self-Hosted Machines for Cloud Agents, allowing teams to run agent tool execution on dynamically scaled infrastructure within their own networks while Cursor continues to manage planning, inference, and agent orchestration in its cloud. The capability is intended for organizations needing direct access to internal services and repositories, specialized hardware such as GPUs or Macs, or custom operating systems and build pipelines, while preserving outbound-only HTTPS connections so Cursor does not initiate access into customer networks. Individual machines can be connected for personal use, while worker pools use queues, team-provided spawn scripts, idle timeouts, and optional hibernation to scale capacity, preserve workspaces, and serve tasks from multiple repositories. Cursor supports integrations with sandbox and compute providers including AWS Lambda, Cloudflare, Coder, Daytona, E2B, Modal, Namespace, and Vercel, and Linux workers now support browser-based computer use alongside Macs. Cursor-hosted environments remain the default, but the new option gives enterprises greater control over where agents run and what systems they can access.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.