Cloudflare launches cf CLI for AI agents and announces the end of Wrangler

In October 2026, Cloudflare opened the public beta of cf, a new open-source CLI written in TypeScript to interact with the company's services. Unlike wrangler, which had been the standard entry point for those working with Workers, D1, Hyperdrive, and other platform products, cf was designed from the start to be operated by both humans and AI agents, according to a report from InfoQ.

The tool is distributed under an Apache 2.0 or MIT license and uses Cloudflare's OpenAPI schemas as the source of truth. This allows cf to cover more than 3,000 API operations, compared to roughly 280 built-in functions in Wrangler. The difference in scale is the first sign that this is not a simple reskin: it is a reconstruction of the command surface built from the API documentation, not from code written by hand by each product team.

Why build a CLI from scratch

Cloudflare explains that Wrangler grew organically, with each product team implementing its own command experience, without a common standard. Matt Taylor, senior product manager, and Samuel Macleod, senior systems engineer, both at Cloudflare, describe the problem:

Wrangler was hand-built with each product team contributing and taking their own approach to their command developer experience. Enforcing patterns across teams was virtually impossible, even across our ~280 command paths. We had inconsistent terminology across d1 info, hyperdrive get, workflows describe as each team came up with their own practices at different times.

Matt Taylor and Samuel Macleod, Cloudflare

According to the two, keeping Wrangler as the base for this change would run into another problem: AI agents had already learned Wrangler's behavior from their training data. Introducing a new CLI avoids conflicting with that prior knowledge baked into the models, allowing cf to adopt agent-oriented design decisions without the compatibility constraints of an already established tool.

The standardization came from an internal pipeline called Forge, Cloudflare's new unified API generation system. Taylor and Macleod explain:

We wanted to both standardize what we had and make a massive expansion, all at once. Forge, Cloudflare's new unified API generation pipeline, enabled us to do this, building on the idea of generating our CLI commands directly from the API schema that powers our API documentation and SDK generation.

Matt Taylor and Samuel Macleod, Cloudflare

What changes in the developer's day-to-day

For those who already write Workers, cf brings three concrete workflow changes. First, configuration moves away from wrangler.toml or wrangler.jsonc to a cloudflare.config.ts file, written in TypeScript. Second, Vite becomes the default development environment, with support for plugins. Third, the CLI was designed for command discovery: instead of memorizing inconsistent names across products, cf itself helps navigate the more than 3,000 available endpoints.

The choice of a TypeScript configuration file, rather than TOML or JSONC, is justified by Cloudflare as a gain for both humans and agents. The company argues that TypeScript offers type checking and LSP support, which allows an agent to understand and modify the configuration more precisely than it could in formats where schema information is less accessible. Programmatic configuration would also reduce duplication across files.

TypeScript split the community

The decision to write the CLI's own binary in TypeScript, not just the configuration format, sparked debate in a popular Hacker News discussion. The central point is predictable for anyone who already works with command-line tools: startup time, portability, and dependency management of an interpreted runtime versus a compiled language. User slowin summarized the criticism:

I don't understand why this is written in TypeScript. This is a great example of how agents can write code (I'm sure they wrote cf), yet having fundamental computer science knowledge is still critical. Do not force your users to manage the dependencies of your CLI. Do write your CLI in a compiled language.

slowin, comment on Hacker News

The criticism is relevant to anyone running CLIs in CI/CD pipelines or in resource-constrained edge environments: a compiled Go or Rust binary tends to start faster and doesn't depend on a Node runtime being installed on the machine. Cloudflare did not directly respond to this point in the available material, but the public defense of the choice focused on the typing gains for configuration, not on the startup performance of the executable itself.

JSON instead of a table, by default

Another behavior change that affects scripts and automations: cf returns JSON output by default, unlike Wrangler, which has historically prioritized human-readable tables. Anyone who wants a table view has to ask for it explicitly. Ashish Ganda, in a LinkedIn post, summarized the rationale behind the choice:

Cloudflare's new cf CLI outputs JSON by default. Not a table. You have to ask for the table (...) Tables are for eyes. JSON is for parsers.

Ashish Ganda, LinkedIn post

In practice, this means that agents invoking cf in an automation chain receive structured data ready to be filtered and transformed, without needing to parse tabular text, something that has historically been fragile in scripts relying on output designed for human eyes.

Wrangler's migration timeline

Cloudflare has already set the roadmap for phasing out Wrangler. The company will deprecate the tool once the open beta of cf ends, release a final major version of Wrangler that directs users to cf, and maintain 18 months of maintenance support to allow time for migration. For teams with Workers infrastructure in production, that's a reasonable window, but not an indefinite one: migrating wrangler.toml to cloudflare.config.ts and reviewing CI scripts that depend on Wrangler's table format becomes a backlog item with a deadline.

What's still not clear, from the material available so far, is the level of feature parity between the two CLIs during the transition period, nor whether teams that automate deployment with Wrangler in legacy pipelines will have an assisted migration path beyond the documentation. For anyone maintaining Workers today, it's worth following the beta's release notes before swapping out production scripts.