Cloudflare, Inc. announced a major update today. The company now supports Cursor Cloud Agents on Cloudflare Sandboxes. This move gives developers a fresh way to run AI coding agents. Moreover, it offers platform teams secure, customer-controlled environments for agent work.
This launch marks another milestone for Cloudflare Sandboxes. Indeed, it pushes Cloudflare closer to becoming the execution layer for agentic applications. Furthermore, the integration builds on Cloudflare’s existing partnerships. These include Devin Outposts and Claude Managed Agents. Together, they reflect a growing trend. Developers want familiar tools, while enterprises demand control over agent execution.
How Cursor Cloud Agents Work with Cloudflare Sandboxes
Cursor Cloud Agents allow developers to assign coding tasks easily. They can do this through the Cursor app, cursor.com, or the mobile app. Additionally, with Cursor Self-Hosted Machines, Cursor still manages the agent loop. This includes inference, planning, and orchestration. However, the actual work now happens on a customer-selected worker.
Consequently, that self-hosted worker can now run inside a Cloudflare sandbox. This sandbox sits within the customer’s own Cloudflare account. As a result, developers keep their existing Cursor workflow intact. They still start and manage agents from Cursor as usual. Meanwhile, the underlying execution location shifts to a controlled environment.
Specifically, tool calls such as terminal, filesystem, and browser actions now run inside these sandboxes. Therefore, teams with strict data residency requirements gain more flexibility. Code, build caches, and secrets stay protected accordingly.
Executive Statements on the Cloudflare-Cursor Integration
“Developers want powerful AI tools that fit naturally into their workflows, and enterprises need those tools to run in environments they control,” said Dane Knecht, Chief Technology Officer at Cloudflare. “Cloudflare Sandboxes gives teams the freedom to use the AI tools they prefer while giving organizations a secure, isolated place to run agent work. Bringing Cursor Cloud Agents to Cloudflare Sandboxes is another step toward making Cloudflare the execution layer for the next generation of agentic applications.”
“SpaceXAI’s goal is to make agents useful wherever developers work,” said Toni Adams, Sr Director of Partnerships at SpaceXAI. “Self-Hosted Machines let teams keep Cursor workflows across desktop, web, and mobile while routing work to infrastructure they operate. Cloudflare Sandboxes give those teams an enterprise-grade option for running agent workloads in a controlled environment.”
Connectivity Model and Enterprise Options
Notably, Cursor Cloud Agents use an outbound connectivity model. A Cursor worker runs the CLI and opens a long-lived outbound HTTPS connection. Thus, Cursor never needs an inbound connection into a customer’s network.
Additionally, individual developers can connect a single worker through My Machines. Meanwhile, enterprise teams can use worker pools as routing targets. These pools let new agent chats wait until a worker becomes available. Subsequently, teams can scale capacity up or down as sessions begin and end.
Data Security During Self-Hosted Operation
Throughout self-hosted operation, repositories, build caches, and secrets remain on customer machines. Meanwhile, only file chunks and Cloud Agent artifacts, such as screenshots and logs, get uploaded. These appear later in pull requests and dashboards.
Finally, teams seeking deeper integration can use the Cloud Agents API. This connects self-hosted machine status and pool routing into existing systems. Developers can explore Cursor Self-Hosted Machines through Cloudflare’s tutorial and Cursor’s official documentation.
Explore IT Tech News for the latest advancements in Information Technology & insightful updates from industry experts!
News Source: Businesswire.com
