Cloudflare launches cf, an agentic CLI covering its entire 3,000-operation API

What Cloudflare shipped

Cloudflare has released cf, a new command-line tool in open beta that exposes the company's entire API — more than 3,000 operations — to both developers and AI agents. According to the Cloudflare blog post announcing the launch, the tool installs globally via npm and is positioned to take over from Wrangler, the company's existing CLI, which covers only around 280 operations.

Agent traffic motivated the build

Cloudflare's own usage numbers explain the urgency. In March 2026, agents accounted for a quarter of all Wrangler usage, up from single-digit percentages a year earlier; in the week before the announcement, that share had climbed to 48%. Agents also behave differently from human users: Cloudflare reports they run nearly twice as many distinct commands per day and are almost four times as likely to invoke six or more commands.

Wrangler, however, grew product by product, with each internal team inventing its own command conventions. Cloudflare points to inconsistent verb choices across commands such as d1 info, hyperdrive get and workflows describe, along with bespoke implementations that saw very little use. Standardising that legacy surface by hand while also multiplying its size was not realistic.

Generated from the API schema

To close the gap, Cloudflare built Forge, a unified generation pipeline that derives CLI commands directly from the OpenAPI schemas that already power its API documentation and SDKs. With extra annotations on those schemas, Forge can produce a command for every endpoint, taking cf from Wrangler's roughly 280 commands to full coverage of the API. Cloudflare describes workflows that now fit in a single tool: create a Worker, deploy it, monitor it, protect it with Cloudflare Access, buy a domain, and put the WAF in front of it.

Agent-first design choices

Several decisions in cf assume the primary user is an agent:

• JSON is the default output, printed compactly for agents and in readable form for humans. With Wrangler, agents habitually appended -- and piped through jq, but many commands only offered tables rendered for people reading a terminal.
• cf cli search lets an agent describe a task in natural language and get back matching commands from a small index built from API descriptions and parameters. cf advertises this command automatically the first time an agent runs --help.
• For parameter-heavy operations such as buying a domain, cf can break the request into a guided, validated form instead of a long chain of flags.

Cloudflare also explains why it chose a brand-new binary rather than evolving Wrangler: language models have absorbed years of Wrangler documentation into training, so drastic changes would collide with learned behaviour. A fresh tool, shipped with its own context injection and AGENTS.md guidance, is less confusing for an agent than reconciling two versions of a familiar one.

TypeScript config and Vite by default

Configuration moves to cloudflare.config.ts, a typed, programmatic format built around a defineConfig helper. Cloudflare says agents with no prior exposure to the format could still identify and edit it correctly, and that LSP-enabled agent tools such as Claude Code and Codex get better suggestions than they did with Wrangler's TOML or JSONC configuration, whose schemas agents rarely consulted. Internally, some Wrangler configuration files shrank by 40% from more than 5,000 lines by deriving environments programmatically from a shared base instead of copying env blocks. Vite also becomes the default local development server, accompanied by a plugin suite for developers and framework authors.

Why it matters

Agents now drive nearly half the traffic on a major developer tool, and Cloudflare is responding by treating them as first-class users rather than a niche audience. The patterns on display here — JSON by default, natural-language command discovery, type-checked configuration, and a CLI generated wholesale from API schemas — are ones Cloudflare itself expects other CLIs to adopt, and they offer a template for any vendor whose API outgrew its tooling. For teams building on Cloudflare, cf also collapses a patchwork of product-specific commands into one interface an agent can navigate end to end.