Cloudflare CLI cf reaches a 1.0 release candidate
The unified Cloudflare CLI stabilises its config format, build output and core commands, but existing beta projects need updating before they can move to it.
Cloudflare shipped the first 1.0 release candidate of cf, its unified CLI for the Cloudflare API and Workers projects, on 17 November. It’s “the release we recommend you try on your own projects” ahead of a final 1.0, and it locks down three things that had still been moving since the beta started in late September: the cloudflare.config.ts config format, the Build Output format that cf build writes and cf deploy reads, and the core commands that create, develop, build and deploy a project.
Getting there breaks things. Build Output moves to a new .cloudflare/output/v1/ layout, prompts and status messages now go to stderr instead of stdout, generated API commands switch to kebab-case (cf accounts billing get-credits), and cf previews deploy takes the preview name as a flag rather than a positional argument. The release needs @cloudflare/vite-plugin 2.0.0-rc.0 or later and Wrangler 4.163.0 or later. It also adds a new way to watch a Worker live:
cf observability tail --worker my-worker --filters '{"status":"error"}'
Why it matters: if you picked up the cf beta early, budget time to update scripts and CI before moving to the release candidate, the config format and command names you built against have changed. Cloudflare still tells existing Wrangler projects to keep using Wrangler, but for anything new, this is the CLI it wants you to start with.
The caveat: this is a release candidate, not the final 1.0. Cloudflare is still asking for feedback, so more changes could land before general availability.