TL;DR
Get the latest gadgets delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
Cloudflare has opened beta access to cf, a new command-line interface generated from its API schema and designed for both AI agents and developers. The company says it covers more than 3,000 API operations, compared with about 280 command paths in Wrangler, and makes JSON the default output. The beta is available through npm; adoption, reliability and the timing of any transition from Wrangler remain unclear.
Cloudflare has opened a beta of cf, a new command-line interface that the company says exposes more than 3,000 Cloudflare API operations, expanding access beyond the roughly 280 command paths available through Wrangler. The tool is designed for AI agents as well as developers, with JSON output by default and commands generated from Cloudflare’s API schemas.
Cloudflare says cf is built on Forge, a new API generation pipeline that turns its API schemas into CLI commands. The company says those schemas already underpin API documentation and software development kits; adding command-specific information lets Forge generate a broader and more consistent command surface. Cloudflare describes the result as access to the entirety of its API, covering more than 3,000 operations.
The beta can be installed globally with npm i -g cf, according to the announcement. Cloudflare says agents can search for commands and receive guidance to identify operations. The CLI uses JSON as its default interface, while offering readable formatting for people and more compact output for agents. The company also says cf introduces a TypeScript configuration file, cloudflare.config.ts, starting with Workers, and makes Vite the default for local development.
Cloudflare frames cf as a new tool rather than a major revision to Wrangler. The company says Wrangler’s command coverage and output conventions grew through contributions from product teams, resulting in different terminology and approaches across products. Its examples of the intended scope for cf include setting up and deploying a Worker, monitoring it, configuring Access and WAF, and purchasing a domain through one CLI. These are examples of potential workflows in the announcement, not independently verified results.
More Cloudflare Operations in One CLI
If the beta works as described, cf could let agents carry out more Cloudflare administration through a single command-line interface, instead of encountering gaps in Wrangler’s command coverage. That matters for workflows spanning several products: an agent could, in principle, deploy an application and then configure related security or domain services using commands generated from the same API foundation.
Making JSON the default also reflects a practical design choice. Agents can select fields from structured output without first interpreting terminal tables, potentially reducing extra parsing steps. Cloudflare says agents now account for a growing share of Wrangler use and make more varied command calls. Those usage figures provide the company’s rationale for a dedicated agent-oriented interface, but they do not by themselves establish that cf will be more reliable or efficient.
Top picks for "agentic cloudflare"
As an affiliate, we earn on qualifying purchases.
From Wrangler to Generated Commands
Cloudflare says Wrangler had accumulated roughly 280 command paths as product teams added support over time. According to the company, teams adopted different command names and output formats, and some built custom interfaces. That made it difficult to standardize the existing CLI while substantially increasing its coverage.
The company says its interest in a broader tool grew as agents began using Wrangler more often. Its report states that agents were responsible for a quarter of Wrangler use in March 2026, up from a single-digit share a year earlier, and reached 48% in the week before publication. Cloudflare also says agents used almost twice as many distinct commands per day and were almost four times as likely to use six or more commands. The announcement does not specify the precise measurement method or baseline for those comparisons.
Cloudflare says it teased work on a solution earlier in the year, then built cf around Forge’s schema-based generation. The company presents the new CLI as a cleaner starting point for agent use than substantially changing Wrangler, whose conventions may already be familiar to people and reflected in agent training data.
““What if your agent could do everything Cloudflare can do?””
— Cloudflare
Beta Scope and Migration Questions
The announcement does not provide independent performance or reliability results for cf, nor does it establish how well its command-discovery features work across the full API. It is also unclear how quickly Cloudflare will add or revise operations, what limitations apply during the beta, or whether every API operation can be completed safely without human input.
Cloudflare does not state whether cf will replace Wrangler, how long both tools will be maintained, or whether existing Wrangler projects will need changes to adopt cf. The reported agent-use figures are company-supplied; the report does not detail the measurement process or clarify the baseline behind the “almost twice” and “almost four times” comparisons. Pricing or other usage costs are not addressed in the supplied announcement.
Testing the Open Beta
Developers can install the open beta globally with npm i -g cf and try its commands against Cloudflare products. The announcement points to Workers as the starting point for the new TypeScript configuration format, with Vite as the default for local development. Cloudflare says it expects to add more agent-focused features, but does not provide a schedule or specific milestones.
Further evidence will come from beta use: how consistently generated commands cover the API, whether agents can find and execute the right operations, and how the new configuration and development defaults fit existing workflows. Cloudflare has not announced a date for a stable release or a decision on Wrangler’s long-term role.
Key Questions
What is Cloudflare cf?
cf is Cloudflare’s new command-line interface, currently in open beta. The company says it is designed for agents and developers and exposes more than 3,000 Cloudflare API operations.
How is cf different from Wrangler?
Cloudflare says Wrangler has about 280 command paths, while cf is generated from API schemas and covers more than 3,000 operations. The new tool also defaults to JSON output. The announcement does not say whether cf will replace Wrangler.
How can developers install the beta?
Cloudflare gives this global npm installation command: npm i -g cf.
What remains uncertain about the launch?
The announcement does not give a stable-release date, a migration plan from Wrangler, or independent evidence about cf’s reliability and coverage in practice. It also leaves the measurement details behind its agent-use statistics unspecified.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
