Cloudflare's new cf CLI puts Wrangler on a deprecation clock, and the default user is now an agent

Cloudflare opened the beta of cf, a new command-line tool meant to replace Wrangler, the CLI nearly every Workers project has been built and deployed with. The new tool is interesting on its own, but the bigger news for working developers is the timeline attached to it. When the beta ends, Cloudflare says it will ship a final major version of Wrangler that points users to cf, then keep Wrangler on maintenance support for 18 months. Wrangler now has an end date, even though the clock has not started yet.

What cf changes

Wrangler grew one product at a time. Cloudflare engineers told InfoQ that each product team contributed its own commands, and that “enforcing patterns across teams was virtually impossible.” The result was roughly 280 commands with inconsistent shapes. cf takes a different approach: its commands are generated from Cloudflare’s API schema, which Cloudflare says lets it cover more than 3,000 API operations with consistent patterns across services.

Three design choices stand out:

• JSON output by default. Cloudflare’s post argues that agents just need JSON, and that if agents become the tool’s main users, JSON should be the default. Human-friendly table output is no longer what you get out of the box.
• Vite as the development and build layer. For Workers that already build with Vite, cf uses the Cloudflare Vite plugin for the dev server with hot module replacement and Rolldown-based builds, instead of Wrangler’s internal tooling.
• TypeScript configuration. Projects move to a cloudflare.config.ts file. Cloudflare says Vite-based Workers are converted for you through cf migrate, and new projects start with cf init.

cf is open source at github.com/cloudflare/cf and installs globally from npm.

Not everything moves at once

The migration story is staged rather than total. Cloudflare says cf will keep delegating dev and deploy to Wrangler for JavaScript Workers that still rely on esbuild, and for Rust and Python Workers. That matters for teams who adopted Python Workers after they reached general availability in September: their path to cf currently runs through Wrangler underneath, so the 18-month window is the number to track for them.

Some details are still unclear. Cloudflare has not given a date for when the beta ends, so the start of the maintenance window is unknown. The post also does not say exactly how cf migrate handles every existing wrangler.toml or wrangler.jsonc setup outside the Vite case. Teams should treat the conversion as something to test on a branch rather than assume it is a one-command switch.

The pushback

The independent reaction has not been all positive. InfoQ’s coverage collected Hacker News criticism of writing a CLI in TypeScript, mostly about startup time and dependency weight, and a LinkedIn comment from Ashish Ganda that summed up the output debate: “Tables are for eyes. JSON is for parsers.” Cloudflare’s response, as InfoQ reports it, is that TypeScript gives agents and editors type-checked configuration and language-server support. Both points hold up. A typed config file catches errors before deploy, and a Node-based CLI is a heavier dependency on minimal CI images than a single binary would be.

What it means for developers

For teams on Workers, the practical work is inventory. Find every place Wrangler shows up: package.json scripts, CI jobs, deploy hooks, and any shell script that parses Wrangler’s table output. Scripts that scrape human-readable text are the most likely to break, and moving them to JSON is worth doing whether or not you adopt cf early. Workers already on the Vite plugin are closest to a clean migration. Projects on esbuild, Rust, or Python have more time, but less certainty about what their end state looks like.

The agent framing matters too. A CLI that covers the full API with predictable commands and machine-readable output is easier for a coding agent to drive safely than one where every product has its own conventions. Cloudflare appears to be betting that a growing share of infrastructure changes will be made by agents acting for developers, and it is redesigning its main developer tool around that.

What to watch

The signals to watch over the next quarter: when Cloudflare sets the beta end date, whether cf migrate handles non-Vite projects without hand edits, and whether third-party CI integrations and community templates switch from Wrangler to cf. Stackmaven’s follow-up coverage will land on or around January 6.

Sources cited

1. Introducing cf, the CLI for Cloudflare (Cloudflare) blog.cloudflare.com
2. Cloudflare Introduces CLI for AI Agents, Sunsetting Wrangler (InfoQ) www.infoq.com
3. cloudflare/cf (GitHub) github.com