Summary
On September 2, 2026, Cloudflare added support for running Cursor Cloud Agents via Cursor self-hosted machines on Cloudflare. Cursor keeps the agent loop, inference, and planning; Cloudflare runs commands, file edits, and repository operations inside Cloudflare Containers that the customer controls, with each assigned session isolated in its own environment.
What changed
Cloudflare shipped a Sandbox SDK tutorial and open-source Workers template that deploys the Worker, Durable Object namespace, container application, R2 bucket binding, and cron trigger needed to execute Cursor Cloud Agent tool calls on Cloudflare infrastructure.
Why it matters
It positions Cloudflare's container and Durable Object stack as a control-plane-free execution layer for a top coding agent, letting teams keep code, file edits, and command execution inside infrastructure they own on Cloudflare's network. It also extends Cloudflare's agent ambitions from hosting bespoke agents to hosting other vendors' agent execution.
Evidence excerpt
Cursor self-hosted machines let you run Cursor Cloud Agents on Cloudflare. Each assigned session runs in its own isolated environment backed by Cloudflare Containers. Cursor hosts the agent loop, inference, and planning. Cloudflare runs commands, file edits, repository operations, and other tools inside infrastructure that you control.