Cloudflare's New cf CLI Is Built for Agents First
Cloudflare's open beta cf CLI gives agents JSON-first access to the full Cloudflare API, with typed configuration and a new open-source generation pipeline called Forge.
Most developer tools still assume the primary user is a human staring at a terminal. Cloudflare's new cf CLI starts from a different premise: the next frequent caller may be an AI agent.
On September 28, 2026, Cloudflare announced cf, an open beta command-line tool designed to mirror the full Cloudflare API and support programmatic TypeScript configuration.1 The launch is interesting not because it is another CLI, but because Cloudflare is explicit about the design target. The company says agent use of Wrangler, its existing developer CLI, has grown sharply: agents accounted for a quarter of Wrangler use in March 2026, and reached 48% the week before the announcement.1
That usage pattern explains the product shape. Wrangler has accumulated around 280 command paths over time. Cloudflare says cf is generated from the API schema through Forge, expanding the reachable surface to more than 3,000 Cloudflare API operations.1 In practical terms, a coding agent should be able to set up a Worker, deploy it, monitor it, protect it with Access, buy a domain, and configure WAF from one tool rather than bouncing between dashboards, partial CLI coverage, and hand-written API calls.
The first notable design choice is output. Cloudflare says cf uses JSON as the default interface: pretty printed for humans, condensed for agents.1 That sounds small until you watch agents use terminals. They already tend to append --json, pipe through jq, and parse only the fields they need. A CLI that treats structured output as the default removes a surprising amount of friction and token waste.
The second design choice is command discovery. With thousands of routes, simply adding commands does not make the tool usable. Cloudflare added cf cli search, a natural-language search interface over the available commands, based on API descriptions and parameters.1 That is a direct concession to agentic workflows: the agent does not need to have memorized every product-specific command before it starts.
The third change is configuration. Cloudflare is introducing cloudflare.config.ts as a new configuration format, beginning with Workers.1 The point is not just that TypeScript is familiar. Typed configuration gives both humans and LSP-aware agents a schema they can inspect while editing. Cloudflare says agents using tools such as Claude Code and Codex benefit from the richer context available through TypeScript and language-server support.1
For the Workers stack, cf also moves Vite to the default path. Cloudflare says the Cloudflare Vite Plugin is now the recommended way to build Workers, for frontend projects and backend APIs alike, and that cf is built on Vite by default.1 Existing Workers can start migration with cf migrate; when the open beta ends, Cloudflare says it will release a final major version of Wrangler that points users toward cf, while maintaining Wrangler for 18 months after the beta ends.1
The open-source piece is Forge, announced the same day. Cloudflare describes Forge as a pluggable generation pipeline for SDKs, CLIs, docs, and libraries, available under the Apache 2.0 license.2 It already generates the output required for cf and is intended to power Cloudflare's API documentation and SDKs over the coming months.2 Cloudflare says Forge runs in CI, generates previews for changes, and is meant to help teams detect generator problems before they break downstream tools.2
The broader signal is clear: agentic development is changing the ergonomics of infrastructure tooling. Agents prefer structured data, searchable command surfaces, typed config, predictable schemas, and fewer human-only formatting choices. Cloudflare is not merely adding "AI features" to a dashboard. It is reshaping the interface between code, cloud APIs, and autonomous development loops.
For teams already building on Workers, D1, R2, KV, Queues, or the rest of Cloudflare's platform, cf is worth watching during the beta. Even if humans still type the commands, the tool is a useful marker for where developer experience is heading: APIs first, generated surfaces, JSON by default, and configuration that both people and agents can reason about without guesswork.