Cloudflare cf CLI: Agent-First Tool Covers the Whole API

Cloudflare has released cf, a new command-line tool that mirrors the company's entire API and is designed primarily for AI agents rather than humans typing commands by hand 12. Alongside the CLI, the company is open-sourcing Forge, the internal SDK generator it uses to produce its tooling 1. The announcement is dated September 28, 2026 1.

The pitch is breadth. Cloudflare says an agent equipped with cf can set up a Worker, deploy it, monitor and observe it, put it behind Cloudflare Access, buy a domain, and front it with the Cloudflare WAF, all through a single tool 2. That covers a range of products that developers previously reached through a mix of dashboards, API calls, and product-specific utilities.

What's actually new

The release has four main pieces.

Agentic command discovery. Cloudflare says cf includes custom search and steering features so an agent can find the right command for a task 2. The company calls these new approaches to command discovery and predicts they will become standard in other CLIs 2. This addresses a real limitation. An API surface as large as Cloudflare's is hard for a model to hold in context, and agents that guess at flags or endpoints tend to fail in confusing ways.

JSON by default. Output is JSON first. It is pretty-printed when a human is reading and condensed when an agent is the consumer, which Cloudflare presents as a way to save as much context as possible 2. This is a useful detail. Token budgets are a constraint for agents, and verbose, human-formatted CLI output wastes them.

TypeScript configuration. A new file, cloudflare.config.ts, is described as the configuration format for all of Cloudflare, starting with Workers 2. Cloudflare also highlights programmatic TypeScript configuration as a core feature of the release 1. The stated benefit is type safety and accuracy that both developers and their agents' language server protocol (LSP) tooling can use 2. When config is typed, an agent gets immediate feedback from the type checker instead of discovering errors at deploy time.

Vite as the default. Cloudflare is making Vite the default for local development, which brings Vite's dev server and a plugin suite aimed at both application developers and framework authors 2.

Why it matters

The framing is explicit. Cloudflare describes cf as built for where software engineering is heading, with agentic development reshaping how software gets built and deployed 2. The company says it has spent the year building tools for that shift and calls cf the culmination of that work 2. It also says the tool was built "from the ground up" with agents in mind and is meant to work even for an agent that has never used cf before 2.

This matters because most CLIs were designed for experienced humans who learn a tool over time. Agents start fresh in every session. A CLI that helps an agent discover commands, returns compact structured output, and validates config through types is designed around that difference rather than adapted to it.

The decision to mirror the entire API also stands out. Agents built on narrower tools often run into gaps where a task needs a capability the tool doesn't expose. Full API coverage removes that ceiling. It also raises the stakes, since the same tool that can deploy a Worker can also purchase a domain 2. Neither source details what guardrails or permission scoping apply to those actions. Teams will likely want answers before handing an agent broad credentials.

The Forge angle

The less prominent part of the announcement may last longer. Releasing Forge, the internal SDK generator, as open source 1 suggests that cf's full API coverage comes from code generation, not hand-maintained commands. That is a reasonable inference given that the two were announced together, though the available material doesn't spell out the link. If it holds, generating the CLI from the API definition would explain how Cloudflare can claim complete coverage and keep it current. Opening Forge could also let other companies build similar agent-ready tooling for their own APIs.

Reading the release

The two accounts agree on the core facts. The Cloudflare blog summary emphasizes full API coverage, TypeScript configuration, and Forge 1, while the longer version adds the agent-facing details: discovery, JSON output, the config file, and Vite 2. They don't contradict each other. The second simply covers more of the developer experience.

The practical case is straightforward. Cloudflare is betting that agents will increasingly operate infrastructure, and that the platforms easiest for agents to drive will win their business. cf is that bet made concrete. Its long-term value will depend on whether the discovery tools hold up on messy real-world tasks and whether safety controls keep pace with an agent's new ability to spend money and change security settings.