Cloudflare has launched the open beta of cf, a new command-line tool designed to give developers and software agents unified access to the entire Cloudflare API. The tool can be installed globally with npm i -g cf.
The launch addresses a gap in Wrangler, which provided commands for only about 280 operations, while the Cloudflare API contains more than 3,000 operations. The company says agent usage of Wrangler rose from single-digit percentages a year ago to 25% in March 2026, then reached 48% in the week before the announcement. Agents also execute nearly twice as many different commands as other users each day, and are about four times more likely to use six or more commands.
An Agent-First Tool
cf makes JSON output the default instead of text tables, allowing agents to filter results directly and reduce context consumption. The tool adds the cf cli search command, which enables natural-language searches for the appropriate operation among thousands of endpoints, based on API descriptions and parameters.
When an operation requires complex human inputs, such as searching for a domain to purchase, the tool can turn API requirements into a form with validated inputs. Cloudflare says the goal is to enable a single agent to create, deploy, and monitor a Worker, then protect it through Cloudflare Access and WAF and purchase a domain, all through one tool.
TypeScript Configuration Instead of Scattered Files
Cloudflare is introducing the cloudflare.config.ts format for managing Workers settings, with the ability to define environments programmatically and benefit from type checking and LSP capabilities. The helpers include definitions for variables and secrets, KV, D1, and R2 resources, queues, AI, Vectorize, and other Workers, in addition to defining scheduled-request, queue, and email triggers in a single block.
The company plans to expand this format to cover Cloudflare management in its entirety, including policies, zones, and DNS. It says that some internal Wrangler configuration files were reduced by 40% after moving to a shared-base environment definition instead of repeating separate blocks.
Forge, Vite, and the Migration Path from Wrangler
The new tool was built using Forge, an open-source unified generation pipeline based on the OpenAPI schemas already used to document the API and create SDK packages. Cloudflare says this approach made it possible to expand coverage from about 280 functions in Wrangler to the entire API surface.
cf uses Vite by default, with the Cloudflare Vite Plugin and Vitest added to provide an integrated development and testing environment for Workers. cf migrate can be used to migrate projects; projects built on Vite are converted to the new configuration file, while the tool continues to delegate builds to Wrangler for projects that use esbuild, as well as for some Rust and Python projects.
After the open beta ends, Cloudflare intends to release a final major version of Wrangler that directs users and agents to cf, while continuing maintenance support for Wrangler for 18 months after the trial ends.
What Changes in Practice?
The fundamental change is not merely the addition of new commands, but the shift of Cloudflare management from a CLI manually written for each product to an interface generated from API schemas, with output and command discovery designed for agents. This could reduce the gap between what Cloudflare provides through its API and what can be executed from the command line, but it places on teams that rely on Wrangler the task of reviewing configuration files and build behavior, particularly in projects that do not use Vite or depend on existing Wrangler integrations.