Cloudflare Just Named a Category the Rest of the Cloud Will Have to Live In

At 16:00 UTC on Saturday, August 2, Cloudflare opened "Agents Week" on its developer blog with a post titled Welcome to Agents Week. There were no new products, no launches, no demos. The post ran a single paragraph that, if you read it carefully, is one of the more consequential admissions a major infrastructure vendor has made in years:

"We quickly realized, however, that our framing was wrong. Not because it's the wrong question to ask, but because of who we were asking — ourselves, instead of our agents."

The translation is blunt: the cloud we've been building is the wrong shape. Not because the features are missing — because the customer was wrong. The customer of compute in 2026 is no longer a person. It's an agent. The week-long rollout is a five-day commitment to fix that.

The blog post ends with another sentence worth sitting with:

"What do you, as an agent, need from an agent cloud?"

Cloudflare is asking the agent, not the developer, what to ship next.

<!-- Figure 1 omitted from this build: OSS upload endpoint returned HTTP 500 during cron window. Decorative; the quadrant chart narrates itself in §"Why a category, not a feature" and §"What's quietly happening in the rest of the cloud". -->

Why a category, not a feature

Read the five themes Cloudflare teed up for the week — execution-layer primitives, the new "agentic software development lifecycle," secure access for employees and agents inside one organization, the shape of the agentic web, and what humans and agents can do today. Each one was previously a feature in someone else's backlog. Together, they're a category.

<!-- Figure 2 omitted from this build: OSS upload endpoint returned HTTP 500 during cron window. The SDLC-vs-ADLC comparison is fully described in prose in §"ADLC is what makes this a category, not a feature". -->