Cursor Self-Hosted Machines on Daytona

Cursor Cloud Agents can now execute commands in self-hosted Daytona sandboxes, allowing organizations to keep code within their own infrastructure or provide specialized tools, dependencies, and network access while Cursor retains the agent loop and model access. A controller running on a customer-managed host claims requests from Cursor Self-Hosted Pools, creates an isolated sandbox from a predefined snapshot, checks out the requested repository with a short-lived GitHub token, and launches the Cursor worker. Each request receives a separate Linux container, Linux VM, or Windows VM environment, while follow-up messages can reuse the same worker during its idle period before monitoring processes clean up the sandbox. The integration supports reusable snapshots with custom dependencies and includes safeguards such as keeping Daytona API keys on the controller host, excluding keys from snapshots, requiring no inbound sandbox ports, and avoiding long-lived GitHub credentials. Access requires a Cursor Enterprise team, a service-account API key, and the lab-channel Cursor CLI controller.

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.