This week Cloudflare dropped a number that made the developer community pause: 48%. That's the share of calls to its existing CLI tool Wrangler that came from AI agents (AI assistants capable of autonomously executing multi-step tasks) last week — a year ago, it was still in the single digits. Around that number, Cloudflare released cf, a brand-new CLI tool fully rewritten for agents.

What this is

cf isn't an upgrade to Wrangler — it's a replacement. The core difference isn't feature count but "target user": cf's default output shifts from human-readable to JSON (a structured data format machines parse more easily), the config file moves from TOML to cloudflare.config.ts, and even search commands are handled in an "agent-friendly" way. Cloudflare's judgment is direct — the primary subject of next-generation software development is no longer human.

Industry view

We see supporters viewing this as inevitable: agents are more diligent than humans, calling nearly twice as many command types per day, with four times the probability of using six or more commands. Letting the most frequent users drive tool evolution is sound product logic.

But we also hear cooler heads. Opposition clusters around three points: one, switching the default output to JSON is a usability downgrade for human-only developers; two, TypeScript configuration is safer but raises the bar to entry; three, Cloudflare's 48% figure comes from its own platform Wrangler, and whether the sample is representative across the industry remains unverified. A deeper worry we share: when tools are designed to serve agents first, will the person at the keyboard be reverse-"agentized", eventually reduced to an "agent operator"?

Impact on regular people

  • For enterprise IT: Over the next two years, we expect code-related tool procurement lists to gain a new line item: "native agent-call support". IT departments will need to reassess internal development standards.
  • For individual careers: Programmers' core competitive edge is shifting partly from "writing code" to "directing agents to write and reviewing agent edits". We see this trend moving from rehearsal to center stage.
  • For consumer markets: No direct short-term impact, but every SaaS (software subscription service) product will face the same question in the future — when half your customers are machines, pricing, APIs, and documentation all need rewriting.