Cloudflare launches agentic CLI “cf” covering the full company API; open beta installable now
Cloudflare’s blog says it launched a new CLI, cf, built for agents, expanding operable surface from Wrangler’s ~280 commands to over 3,000 Cloudflare API operations. JSON is the default output, with cloudflare.config.ts and Vite as the default local stack. An open beta can be installed globally now.
Cloudflare’s blog says agent use of Wrangler surged over the past year—agents were a quarter of Wrangler use in March 2026 and reached 48% last week; agents use almost twice as many distinct commands per day and are almost four times as likely to use six or more. Wrangler only covers around 280 operations while Cloudflare offers thousands. The company introduces cf so agents can use “every Cloudflare product.”
Features cited: bespoke search/steering so agents find commands; JSON as the default interface (pretty for humans, condensed for agents); cloudflare.config.ts as the new config format for Cloudflare as a whole, starting with Workers, bringing TypeScript to editor LSPs; Vite as the default local dev/build path. Commands are generated via Forge from OpenAPI schemas, expanding from ~280 to over 3,000 operations. Example flows: create a Worker, deploy, observe, protect with Access, buy a domain, and put WAF in front—from one tool.
Migration: cf migrate; Vite-built Workers convert to cloudflare.config.ts; projects still on Wrangler/esbuild keep cf delegating to Wrangler. When the open beta ends, a final major Wrangler will point users and agents to cf, with 18 months of maintenance support after beta ends. Static sites can cf deploy without a config; new projects use cf init. The tool is open source with issues on GitHub. Agent-share and coverage figures are company claims.
Sources
- Introducing cf: the agentic CLI for the entire Cloudflare API — blog.cloudflare.com