Cloudflare on September 28, 2026 introduced cf, a new command-line interface it says is designed primarily for AI coding agents and covers the company's entire API surface. The tool is available as an open beta and can be installed globally with npm i -g cf, according to the company.
What Cloudflare announced
Cloudflare said cf replaces the roughly 280 command paths that its existing CLI, Wrangler, accumulated over time with coverage of "over 3,000 operations" across the Cloudflare API.
The company said the expansion was made possible by Forge, which it described as Cloudflare's new unified API generation pipeline that generates CLI commands directly from the OpenAPI schemas already used for its API documentation and SDKs.
Cloudflare said Wrangler had been hand-built by individual product teams, producing inconsistent terminology across commands such as d1 info, hyperdrive get and workflows describe.
Why Cloudflare says it built for agents
Cloudflare said agent use of Wrangler has grown sharply: agents accounted for a quarter of Wrangler use in March 2026, up from single-digit percentages the year prior, and reached 48% last week. It added that agents use almost twice as many distinct commands per day and are almost four times as likely to use six or more commands.
In cf, JSON is the default interface — pretty printed for humans and condensed for agents, which the company said saves context. Cloudflare noted that in Wrangler many commands returned unicode tables rather than JSON, costing agents time and tokens.
A new command, cf cli search, lets an agent describe in natural language what it needs to do and returns a list of matching commands from a small search index based on API descriptions and parameters. Cloudflare said agents are automatically told about the command the first time they run –help.
Configuration and build changes
Cloudflare introduced cloudflare.config.ts, a TypeScript configuration format that it said brings type checking and language server protocol support to both developers and agents, starting with Workers. The company contrasted it with TOML, which it said had no accessible schema, and JSONC, whose linked schema agents rarely used.
Cloudflare said some internal Wrangler configuration files of over 5,000 lines have been condensed by 40% by programmatically defining environments from a shared base. Helper functions cover bindings such as KV, D1, R2, queues, AI and Vectorize, plus triggers for fetch, scheduled, queue and email.
Vite becomes the default build tooling, replacing the esbuild-based bundler and custom dev server in Wrangler. Cloudflare said cf will continue to delegate dev and deployment to Wrangler for JavaScript Workers that still need esbuild, as well as for Rust and Python Workers.
Migration timeline
Existing projects can move with cf migrate, which Cloudflare said converts Workers that already build with Vite to cloudflare.config.ts. New projects can use cf init or cf deploy.
When the open beta ends, Cloudflare said it will release a final major version of Wrangler that directs users and agents to cf, and will provide maintenance support for Wrangler for 18 months after the beta ends. The company said cf is open source and issues can be reported on its GitHub repository.
What to do
- Install the open beta globally with npm i -g cf to try the new CLI.
- Run cf migrate to convert an existing Worker; projects that already build with Vite are converted to cloudflare.config.ts automatically.
- Use cf init to start a new Hello World project, or cf init/deploy to configure a new project and install the Cloudflare Vite Plugin.
- Deploy static sites with cf deploy, which Cloudflare says still requires no configuration file.
- Use cf cli search to have an agent find the right command in natural language.
- Plan migration off Wrangler within the 18-month maintenance window Cloudflare says will follow the end of the beta.
- Report problems through the cf GitHub repository.
Key facts and where they come from
- Agent share of Wrangler use reached 48% last week, up from a quarter in March 2026.
In March 2026, agents were responsible for a quarter of Wrangler use, up from single-digit percentages the year prior. Last week, agent usage reached 48%.
- cf covers more than 3,000 API operations versus about 280 in Wrangler.
This enables us to expand cf from the ~280 functions that Wrangler had built up over time, to cover the entirety of the Cloudflare API surface of over 3,000 operations.
- The CLI is available now as an open beta via npm.
Install the open beta today globally and run it from anywhere: npm i -g cf
- JSON is the default output format in cf.
JSON is the default interface, pretty printed for humans and condensed for agents for maximum context savings.
- Commands are generated from API schemas through Cloudflare's Forge pipeline.
Forge — Cloudflare’s new unified API generation pipeline — enabled us to do this, building on the idea of generating our CLI commands directly from the API schema
- Wrangler gets 18 months of maintenance support after the beta ends.
We’ll continue to provide maintenance support for Wrangler for 18 months after the beta ends, to give you time to migrate.
- Internal configuration files shrank by 40%, Cloudflare said.
Some Wrangler configuration files inside Cloudflare have been condensed by 40% from over 5,000 lines