Cloudflare cf CLI Replaces Wrangler With Agent-First Design

What Cloudflare shipped

Cloudflare has released cf, a new command-line interface now in open beta. It is designed to be used by AI agents as much as by human developers. The tool is open source and written in TypeScript. It emphasizes structured output and built-in command discovery, and it covers more than 3,000 API operations. Wrangler, the CLI it replaces, handled roughly 280 13.

The launch was announced on September 28, 2026, as part of Cloudflare's Birthday Week. Alongside cf, the company open-sourced Forge, the internal SDK generator behind the effort 2. Cloudflare's pitch is that a single tool can now span the whole platform. An agent could stand up a Worker, deploy and monitor it, gate it behind Cloudflare Access, register a domain, and put the Cloudflare WAF in front of it without switching tools 4.

The Wrangler sunset clock

The bigger operational news is what happens to Wrangler. Cloudflare plans to deprecate it once cf leaves beta, then support migration for 18 months 1. That gives teams running production Workers a defined window, though the clock does not start until general availability. One developer writing on note.com framed the practical concern clearly. For existing Wrangler users, the question is less about cf's new conveniences and more about when existing Workers can safely move over and what has to change when they do 2. That author also noted they had not yet tested cf hands-on and were working from Cloudflare's official announcement, which reflects how early this transition still is 2.

Why build a new tool instead of fixing the old one

Cloudflare gives two reasons for starting fresh, and the second is unusual.

The first is organizational debt. Senior product manager Matt Taylor and senior systems engineer Samuel Macleod explained that Wrangler was assembled by hand, with each product team contributing commands in its own style. Enforcing consistent patterns across those teams was close to impossible 3. Generating the CLI from a single source, which is presumably where Forge comes in, addresses that inconsistency at the root.

The second reason is about models, not people. Cloudflare argues that large language models have already absorbed a lot of learned behavior around Wrangler's commands and conventions. Redesigning Wrangler in place would put agents' training data in conflict with the tool's new behavior. A new name sidesteps that and frees cf from backward-compatibility constraints 13. Vendors used to worry only about breaking human muscle memory. Cloudflare is now treating model memory as a design constraint, and that rationale may become more common.

Agent-first design choices

Several defaults show who the primary user is meant to be. JSON is the standard output format. It is pretty-printed for humans and condensed for agents to conserve context-window space 4. Cloudflare also built dedicated search and steering features so an agent that has never encountered cf can locate the right command. The company predicts these discovery tools will become standard across CLIs 4.

Configuration is changing too. A new cloudflare.config.ts file becomes the configuration format for Cloudflare as a whole, starting with Workers. The aim is to bring TypeScript type safety, and the language-server feedback that comes with it, to both developers and their agents 4. Vite also becomes the default local development server, with a plugin suite for developers and framework authors 4.

Where friction is likely

The TypeScript configuration move is the clearest flashpoint. Typed config gives an agent working through a language server real guardrails, since mistakes surface before deployment rather than after. But making a TypeScript file the configuration format for all of Cloudflare is an opinionated choice. It also means moving away from Wrangler's existing configuration files. Teams whose stacks are not centered on TypeScript, or who value declarative, non-executable config, have reason to question whether that trade-off suits them. The new defaults, from JSON output to Vite, also add migration surface on top of the CLI swap itself.

The takeaway

The four accounts agree on the facts: a broader, generated, agent-oriented CLI, and a Wrangler deprecation backed by an 18-month runway. They differ mainly in emphasis. Cloudflare and the trade press highlight capability and agent ergonomics 134. Practitioners focus on migration timing and risk 2.

The more important shift is strategic. Cloudflare is betting that infrastructure will increasingly be operated by agents, and it is willing to retire a familiar tool to optimize for them. The expansion from about 280 to over 3,000 operations is a substantial upgrade on its own. Whether developers accept the opinionated parts, especially TypeScript configuration, will likely decide how smoothly the Wrangler sunset goes. For now, the sensible approach for most teams is to evaluate cf during the beta and plan migrations around the post-GA deprecation window.