The integration<\/a> builds on Cloudflare\u2019s work with other leading AI agent platforms, including Devin Outposts <\/a>and Claude Managed Agents<\/a>, and reflects a simple shift in how agentic software is being deployed: developers want to keep the tools they already use, while enterprises want control over where agent work runs and how it accesses code, systems, and secrets. Cloudflare Sandboxes are becoming a natural execution layer for that model: secure, isolated environments where agent work can run closer to a customer\u2019s code, systems, and security requirements.<\/p>\n \nCursor Cloud Agents let developers assign coding tasks from the Cursor app, cursor.com, or the Cursor mobile app. With Cursor Self-Hosted Machines, Cursor continues to run the agent loop, including inference, planning, and orchestration, while the agent gets work done on a customer-selected worker. In SpaceXAI\u2019s model, a worker is the customer-operated machine or environment that executes agent tasks; it is separate from Cloudflare Workers<\/a>, Cloudflare\u2019s serverless developer platform. With Cloudflare Sandboxes, that self-hosted worker can run in a sandbox environment in the customer\u2019s Cloudflare account.<\/p>\n \nDevelopers keep the Cursor workflow they already use: they still start and manage agents from Cursor, and Cursor still routes the work and streams results back to the user. What changes is where the work happens. Tool calls, including terminal, filesystem, and browser actions, run inside customer-controlled Cloudflare sandbox environments, which matters for teams with strict requirements around where code, build caches, and secrets live. For organizations using Cursor Self-Hosted Machines across different execution environments, Cloudflare Sandboxes provide another controlled option for running agent workloads.<\/p>\n \n\u201cDevelopers want powerful AI tools that fit naturally into their workflows, and enterprises need those tools to run in environments they control,\u201d said Dane Knecht, Chief Technology Officer at Cloudflare. \u201cCloudflare 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.\u201d<\/p>\n \nCursor Cloud Agents run via self-hosted machines use an outbound connectivity model. A Cursor worker runs the Cursor CLI and opens a long-lived outbound HTTPS connection to Cursor\u2019s backend, where agent tool calls are sent over that connection. Cursor does not need to open an inbound connection into the customer\u2019s network; teams can use the quickstart guide<\/a> to configure a Cursor worker and connect it to their environment.<\/p>\n \n“SpaceXAI\u2019s goal is to make agents useful wherever developers work,\u201d said Toni Adams, Sr Director of Partnerships at SpaceXAI. \u201cSelf-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.\u201d<\/p>\n \nThe integration supports Cursor\u2019s Self-Hosted Machines workflow for individual developers and teams. Developers can connect a single worker through My Machines, while enterprise teams can use Cursor self hosted worker pools<\/a> as named routing targets that allow new agent chats to wait until an available worker claims them. Teams can create pools for different execution environments, then use pool orchestration<\/a> to watch demand, start worker capacity when needed, and release it when sessions end.<\/p>\n \nDuring self-hosted operation, repositories, build caches, and secrets stay on the customer’s machines. File chunks read by the model during inference, along with Cloud Agent artifacts such as screenshots, videos, and log references, are uploaded so they can appear in pull requests and dashboards. Teams that want to integrate self-hosted machine status or pool routing into their own systems can also use the Cloud Agents API<\/a>.<\/p>\n \nDevelopers and platform teams can learn more about Cursor Self-Hosted Machines by visiting the Cloudflare tutorial<\/a>, the Cursor quickstart<\/a>, or the Cursor worker pools<\/a>, pool orchestration<\/a>, and Cloud Agents API<\/a> documentation. To see how Cloudflare Sandboxes support other agent platforms, read more about Devin Outposts on Cloudflare<\/a> and Claude Managed Agents on Cloudflare<\/a>.<\/p>\n About Cloudflare<\/b><\/p>\n \nCloudflare, Inc. (NYSE: NET) is the leading connectivity cloud company. It empowers organizations to make their employees, applications and networks faster and more secure everywhere, while reducing complexity and cost. Cloudflare\u2019s connectivity cloud delivers the most full-featured, unified platform of cloud-native products and developer tools, so any organization can gain the control they need to work, develop, and accelerate their business.<\/p>\n \nPowered by one of the world\u2019s largest and most interconnected networks, Cloudflare blocks billions of threats online for its customers every day. It is trusted by millions of organizations \u2013 from the largest brands to entrepreneurs and small businesses to nonprofits, humanitarian groups, and governments across the globe.<\/p>\n \nLearn more about Cloudflare\u2019s connectivity cloud at cloudflare.com\/connectivity-cloud<\/a>. Learn more about the latest Internet trends and insights at https:\/\/radar.cloudflare.com<\/a>.<\/p>\n \nFollow us: Blog<\/a> | X<\/a> | LinkedIn<\/a> | Facebook<\/a> | Instagram<\/a><\/p>\n Forward-Looking Statements<\/b><\/p>\n \nThis press release contains forward-looking statements within the meaning of Section 27A of the Securities Act of 1933, as amended, and Section 21E of the Securities Exchange Act of 1934, as amended, which statements involve substantial risks and uncertainties. In some cases, you can identify forward-looking statements because they contain words such as \u201cmay,\u201d \u201cwill,\u201d \u201cshould,\u201d \u201cexpect,\u201d \u201cexplore,\u201d \u201cplan,\u201d \u201canticipate,\u201d \u201ccould,\u201d \u201cintend,\u201d \u201ctarget,\u201d \u201cproject,\u201d \u201ccontemplate,\u201d \u201cbelieve,\u201d \u201cestimate,\u201d \u201cpredict,\u201d \u201cpotential,\u201d or \u201ccontinue,\u201d or the negative of these words, or other similar terms or expressions that concern Cloudflare\u2019s expectations, strategy, plans, or intentions. However, not all forward-looking statements contain these identifying words. Forward-looking statements expressed or implied in this press release include, but are not limited to, statements regarding the capabilities and effectiveness of Cloudflare Sandboxes and Cloudflare\u2019s other products and technology, the benefits to Cloudflare\u2019s customers from using Cloudflare Sandboxes and Cloudflare\u2019s other products and technology, Cloudflare\u2019s technological development, future operations, growth, initiatives, or strategies, and comments made by Cloudflare\u2019s made by Cloudflare\u2019s Chief Technology Officer and others. Actual results could differ materially from those stated or implied in forward-looking statements due to a number of factors, including but not limited to, risks detailed in Cloudflare\u2019s filings with the Securities and Exchange Commission (SEC), including Cloudflare\u2019s Quarterly Report on Form 10-Q filed on August 6, 2026, as well as other filings that Cloudflare may make from time to time with the SEC.<\/p>\n \nThe forward-looking statements made in this press release relate only to events as of the date on which the statements are made. Cloudflare undertakes no obligation to update any forward-looking statements made in this press release to reflect events or circumstances after the date of this press release or to reflect new information or the occurrence of unanticipated events, except as required by law. Cloudflare may not actually achieve the plans, intentions, or expectations disclosed in Cloudflare\u2019s forward-looking statements, and you should not place undue reliance on Cloudflare\u2019s forward-looking statements.<\/p>\n \n\u00a9 2026 Cloudflare, Inc. All rights reserved. Cloudflare, the Cloudflare logo, and other Cloudflare marks are trademarks and\/or registered trademarks of Cloudflare, Inc. in the U.S. and other jurisdictions. All other marks and names referenced herein may be trademarks of their respective owners.<\/p>\n View source version on businesswire.com: <\/span>https:\/\/www.businesswire.com\/news\/home\/20260901365900\/en\/<\/a><\/span><\/p>\n \nCloudflare, Inc. KEYWORDS:<\/b> California United States United Kingdom Germany Singapore Southeast Asia Spain North America Ireland Asia Pacific Europe<\/p>\n INDUSTRY KEYWORDS:<\/b> Data Management Security Technology Software Networks Artificial Intelligence<\/p>\n<\/p>\n
\n
Daniella Vallurupalli
\n
Vice President, Head of Global Communications
\n
press@cloudflare.com<\/a><\/p>\n
![\"Logo\"](\"https:\/\/mms.businesswire.com\/media\/20260901365900\/en\/738100\/3\/cf-logo-h-rgb.jpg\"){kind=logo}
<\/td>\n<\/tr>\n