September 29, 2026Agent-OperableToolInfrastructure

Cloudflare's New CLI Was Built for Agents, Because Agents Are Already Half Its Users

48%. That is the share of Wrangler usage that came from AI agents last week, up from 25% in March. Cloudflare published the number on September 28 alongside the reason it matters: a new command-line tool, cf, designed from day one for agents as the primary user.

The scope is the first change. Wrangler covered about 280 commands. cf covers the entire Cloudflare API, over 3,000 operations, from deploying Workers to domains to security policies, in one binary (npm i -g cf). The second change is the interface. JSON is the default output, pretty-printed for humans and condensed for agents. cf cli search lets an agent ask in plain English which command it needs instead of reading docs. The tool injects agent context and ships AGENTS.md files to cut down on wrong guesses. Config moves to a typed cloudflare.config.ts, Vite is the default dev server, and cf migrate converts old Wrangler projects.

The stat buried in the post is the more interesting one: agents use nearly twice as many distinct commands per day as humans. People learn five commands and stay there. Agents wander across the whole surface. That is why a 280-command CLI was the bottleneck, and why every platform with a CLI should expect the same curve.

This is what agent-operable infrastructure looks like when a vendor takes its own telemetry seriously. Not a chatbot bolted onto the dashboard, but the machine interface redesigned for the machine. When half your users are agents, the CLI is the product. cf is open source and in beta at github.com/cloudflare/cf.

Link: blog.cloudflare.com/cloudflare-cf-cli-launch
← Previous
Shopify Lets Agents Pay. Amazon Still Won't.
Next β†’
Google Is Killing Gems and Calling Them Skills. The Word Won.
← Back to all articles

Comments

Loading...
>_