Image: GitHub
Why it mattersZones, DNS, storage, Workers, and security settings now live behind one typed CLI, which is one less tool for a Cloudflare developer or their coding agent to keep straight.
A Cloudflare developer used to open the dashboard for DNS, the Wrangler CLI for Workers, and a REST client for everything else.
Cloudflare released cf on GitHub last month and opened its public beta over the past two weeks, pitching it as "the agentic CLI for the entire Cloudflare API". The repository, published under Apache 2.0, carries 686 stars eleven days after it was first pushed. The documentation at developers.cloudflare.com/cf, last updated September 29, says cf includes more than 2,900 commands, most of them generated from the schemas that describe the Cloudflare API.
What is in the box
Four pieces, from the documentation: a command for every public Cloudflare API endpoint, a new TypeScript configuration file called cloudflare.config.ts that replaces wrangler.jsonc and wrangler.toml for Workers projects, three project-level commands (cf dev, cf build, cf deploy) that call the right underlying tool for a given framework, and a plain-language command search (cf cli search) that returns the command for a described task.
The TypeScript config is the piece that changes how agents work with Cloudflare. A cloudflare.config.ts file is read by an editor's language server, which means autocomplete for bindings and triggers, and the same information is available to an agent reading the project.
Living with Wrangler
Wrangler is not retired. Cloudflare says cf and wrangler coexist for Workers projects. A team can run cf resource commands (zones, DNS, storage) alongside an existing Wrangler project without changing it. Before running cf dev, cf build, or cf deploy inside a Wrangler project, Cloudflare asks developers to convert the project with cf migrate, which rewrites wrangler.jsonc or wrangler.toml as cloudflare.config.ts.
The documentation calls out one honest caveat: "cf is in beta. Commands, configuration, and Build Output can change before the stable release." The 103 open issues on the repository as of October 2 suggest the beta label is doing real work.
JSON is the default output, pretty-printed for a person and condensed for an agent. That is the deliberate shape of the whole project: Cloudflare has pulled the API, the Workers tooling, and the search layer behind one typed interface a human can read and a coding agent can call. The cf cli search command is where that pays off for an agent, which can describe a task in plain language ("create a DNS record for a subdomain", "list R2 buckets in this account") and get back the exact command rather than searching the dashboard or reading the API reference.
For a team using more than one Cloudflare product, the trade is a new CLI to learn against one less jump between the dashboard, Wrangler, and curl. A SEO or infrastructure team that scripts against the Cloudflare API through shell has the clearest reason to migrate; a Workers-only team can watch the beta label and plan the Wrangler to cloudflare.config.ts conversion for a quieter week.
Source
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.
