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 announced an open beta of cf, a command-line interface designed to give agents access to more than 3,000 Cloudflare API operations. The company says it uses JSON by default and adds tools to help agents find commands; the source does not provide independent performance results or a beta end date.
Cloudflare has opened the beta of cf, a new command-line interface designed to let software agents work across more than 3,000 Cloudflare API operations. The launch addresses a limit in Wrangler, Cloudflare’s existing developer CLI, which the company says covered about 280 operations and offered uneven command and output patterns across products.
Cloudflare says cf commands are generated through Forge, its unified API generation pipeline. The pipeline uses the OpenAPI schemas already associated with Cloudflare’s API documentation and software development kits, with additional annotations to produce CLI commands. The company presents this approach as a way to apply a more consistent structure across its products while expanding the number of available operations.
The new CLI makes JSON the default output, rather than relying on terminal tables designed for people. Cloudflare says this is intended to make results easier for agents to filter and use, reducing the need to request JSON separately or extract information from human-oriented output. The company also describes bespoke search and steering tools to help agents discover commands. For tasks that require a person to enter information, such as buying a domain, cf can present validated inputs as a form.
Cloudflare says cf is available as an open beta and gives this installation command: npm i -g cf. The company also identifies cloudflare.config.ts as a new configuration format, beginning with Workers, and says it plans to make Vite the default for local development. The supplied announcement does not specify a beta end date or a migration schedule for Wrangler users.
One CLI Across Cloudflare Products
If cf reaches the coverage Cloudflare describes, agents could use one interface to perform tasks that span several of the company’s products. Cloudflare gives the example of setting up and deploying a Worker, monitoring it, applying Cloudflare Access, buying a domain, and configuring WAF protection. Today, the company says, Wrangler does not expose the full API surface through its command paths.
The change also puts more of the interaction between agents and Cloudflare into a machine-readable format. JSON by default may make it simpler for an agent to inspect a response and pass selected values into another command. The practical effect will depend on how reliably the discovery features identify the right operation, how the generated commands behave in real projects, and how the beta handles tasks that need human input or authorization. The announcement describes Cloudflare’s design goals; it does not report independent tests of agent success, time saved, or error rates.
From Wrangler to Generated Commands
Cloudflare says agent use of Wrangler grew over the year before the announcement. According to the company, agents accounted for a quarter of Wrangler use in March 2026, up from single-digit percentages the year before, and reached 48% the week before publication. Cloudflare also says agents used almost twice as many distinct commands per day as other users and were almost four times as likely to use six or more commands. The source provides no measurement method or baseline details beyond those comparisons, so these figures should be read as company-reported usage data.
Wrangler was built over time by different Cloudflare product teams. The company says that process led to inconsistent naming and command experiences, and that some custom-built interfaces saw little use. It says generating commands from API schemas through Forge is intended to standardize the interface and extend coverage. Cloudflare describes cf as a new tool designed for agents, rather than an incremental revision of Wrangler, partly because agents may already have learned Wrangler’s existing conventions from documentation and other material.
““cf gives your agent access to the entire Cloudflare API.””
— Cloudflare
Beta Coverage and Migration Questions
The announcement describes cf as covering the Cloudflare API surface, but it does not list operations that are unavailable, explain whether every operation is equally mature in the beta, or provide independent validation of the stated coverage. It also does not say how long the open beta will run, what support or stability guarantees apply, or whether the CLI will eventually replace Wrangler.
Cloudflare reports rising agent use of Wrangler, but the source does not explain how it defines agent usage, how the measurements were collected, or whether the same method was used for each comparison. The announcement also gives no results from user trials that would show how often command search finds the correct operation, or how cf handles mistakes and tasks with consequential effects. Those details will matter as developers assess whether to rely on the beta for work across their Cloudflare accounts.
Testing the Open Beta
Developers can install the beta with npm i -g cf and try it with their own Cloudflare workflows. The next evidence to watch for includes updates to the beta, documentation on command coverage and known limitations, and details on the rollout of cloudflare.config.ts and Vite defaults. Cloudflare has not announced dates for those milestones in the supplied material.
For teams already using Wrangler, the immediate next step is to compare the commands and workflows they depend on with cf’s beta behavior. Cloudflare has not specified a migration plan, so the timing and process for any change remain open.
Key Questions
What is Cloudflare cf?
cf is Cloudflare’s new command-line interface, released in open beta. The company says it is designed for agents and can expose more than 3,000 API operations.
How does cf differ from Wrangler?
Cloudflare says Wrangler had about 280 command paths, while cf is generated from API schemas through Forge to cover the broader API surface. Cf also uses JSON by default and includes command discovery features aimed at agents.
How can developers install the beta?
Cloudflare provides the command npm i -g cf for a global installation. The announcement does not describe beta support terms or an end date.
Does cf replace Wrangler?
Cloudflare describes cf as a new CLI but does not say that it will replace Wrangler or provide a migration schedule. Whether and when existing users should move their workflows remains unclear.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
