Cloudflare is scrapping its old command-line tool and starting fresh, with a new version that spans the whole company’s API surface. It is a wager that a clean start beats a fix, and it follows a year during which agents — the automated AI systems that take over development tasks — have claimed an ever-larger share of Wrangler’s daily use.
Today marks the launch of cf, an open beta release. The company reports that agents accounted for a quarter of Wrangler use in March 2026, a rise from single-digit percentages the previous year. Just last week, agent usage hit 48%.
The Case Against Wrangler
Each product team at Cloudflare crafted its own commands and its own method of handling them when building Wrangler by hand. This approach gave rise to inconsistency across the command paths. The company points to specific examples to illustrate the issue: d1 info, hyperdrive get, and workflows describe all refer to related actions using different terminology.
Across multiple teams, entirely custom experiences were built across thousands of lines of code, only to end up being used extremely rarely. Each team took a different approach to solving the same problems.
The announcement opens with a statement that “We had inconsistent terminology across d1 info, hyperdrive get, workflows describe as each team came up with their own practices at different times,” which is a quotation that has been lifted from the text.
Cloudflare aimed to consolidate its existing offerings even as it grew immensely. Its new unified API generation pipeline, called Forge, made both goals possible at once. Every product Cloudflare offers comes with an OpenAPI schema, and adding just a small amount of extra detail to those schemas lets Forge produce a command-line interface from them.
Wrangler’s accumulated collection of roughly 280 functions enabled cf to extend its reach across the full Cloudflare API surface, which covers more than 3,000 operations.
What cf Actually Does
The announcement lists four core features:
- Bespoke search and steering help agents find the command they need for any action.
- JSON is the default interface, pretty-printed for humans and condensed for agents to save context.
- cloudflare.config.ts is the new configuration format, starting with Workers and bringing TypeScript safety to the language server protocol (LSP).
- Vite becomes the default local development server, with a plugin suite for developers and framework authors.
The firm contends that launching a fresh CLI that agents have never used before is the cleanest approach it can take. The design choices, context additions, and AGENTS.md documents it can tack on make a transition smoother than forcing an agent to grasp the significant distinctions between two editions of a familiar tool.
Wrangler commands often return tables built for human eyes, which forces agents to parse them. Agents instead want JSON, so they add –json to every command and then filter the output with jq to get just a subset of fields.
“In cf we’re taking the opposite stance: agents just need JSON, and if agents are the future primary user of this tool, it should be the default,” the announcement reads.
When people need to put in personal effort for a task, such as finding a domain to purchase, cf offers a form-based method. It breaks down API demands into a set of checked inputs, which makes buying a domain with complicated requirements easy to follow.
The Agent Problem
Human users lag behind agents when it comes to Wrangler command usage. Agents employ nearly twice the number of distinct commands daily, and they are also almost four times more inclined to run six or more commands.
The change serves as a working test. Should agents pick up cf without delay, the shift will have proven worthwhile. Should they find the new command paths difficult to master, the trouble will have been genuine.
The company knows the danger. Altering how Wrangler operates contradicts what has been learned over time, and a major shift would likely happen given the size of the improvements Cloudflare is aiming for.
What This Means for Developers
What makes the move stand out is its framing of agents as the principal users of the CLI, even though humans are actually one step removed from using it themselves. Having agents filter results and return them in whatever format you request beats supplying tables that you will never likely read directly.
Npm i -g cf installs the cf beta globally, and the company is deploying it with a few agent-focused features already included, with additional ones on the way.
The announcement positions cf as a tool for the path ahead in software engineering, where development driven by agency is reshaping how software gets built and put into service. Cloudflare has kept its attention on supplying tools to back up this change, and cf marks the high point of that work.
In the near future, the firm expects agentic command discovery tools in cf to move from uncommon to common across many CLIs.
Key Numbers
- Wrangler commands: ~280
- Cloudflare API operations: over 3,000
- Agent share of Wrangler use in March 2026: a quarter
- Agent share of Wrangler use last week: 48%
- Commands per day from agents vs humans: agents use almost twice as many distinct commands
- Agents using six or more commands: almost four times as likely as humans
Cloudflare believes a fresh start beats a fix. Forge starts from scratch, so every path to a command follows the same design. Agents can learn the new tool without bringing along old habits.
Months of preparation have gone into this. Now the open question is whether agents will be drawn in to begin using cf.
Source material: “Cf: The Agentic CLI for the Cloudflare API,” cloudflare.com.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.