Sulat.com / Writing on AIThursday, November 19, 2026
Developer Tools/18 November 2026

Cloudflare’s cf CLI reaches a 1.0 release candidate and adds live log streaming

Cloudflare says cf 1.0.0-rc.1 locks in the config format, Build Output and deploy commands, and adds live log streaming. Beta users need a new Build Output folder and newer Vite and Wrangler versions.

3D Cloudflare logo floating beside a dark terminal streaming glowing orange log lines above a nearly full release-candidate bar

At a glance

  • Cloudflare says cf 1.0.0-rc.1 is the release it recommends developers try on their own projects, after cf spent from late September in beta, with feedback wanted before 1.0.
  • Cloudflare says it expects the cloudflare.config.ts format, the Build Output format and the init, dev, build and deploy commands to stay stable through 1.0, along with most API commands.
  • The release candidate adds cf observability tail, which streams live logs as newline-delimited JSON for one Worker, a zone or a whole account; the beta docs had sent users to wrangler tail.
  • Build Output moves to .cloudflare/output/v1/, and the release needs @cloudflare/vite-plugin 2.0.0-rc.0 or later for Vite projects and Wrangler 4.163.0 or later for legacy builds.
  • A few generated API commands are renamed without aliases, such as cf workers secrets bulk becoming cf workers secrets bulk-edit, and Cloudflare's changelog doesn't give a release date for 1.0.

Cloudflare has released a 1.0 release candidate of cf, its command-line tool for the whole Cloudflare API, the company says in a changelog post dated 17 November. Version 1.0.0-rc.1 calls the config format, the Build Output format and the commands that create, develop, build and deploy projects stable, and it adds live log streaming with cf observability tail.

Matt “TK” Taylor, who works on Cloudflare’s developer and agent platform, announced the release on X. Taylor wrote that all the local development and deployment commands are now stable and asked developers to try them on a Wrangler project. Wrangler is Cloudflare’s existing command-line tool for Workers, its platform for running code on Cloudflare’s network.

npm install --global cf@latest

What cf is

cf went into beta on 28 September. Cloudflare’s launch post says cf covers the public Cloudflare API, where Wrangler covers around 280 operations, and the docs count more than 2,900 commands. Cloudflare said agents made up 48% of Wrangler use at the time, up from a quarter in March. Most cf API commands print JSON, and cf cli search finds a command from a plain-language description of a task.

When the beta ends, Cloudflare says it will release a final major version of Wrangler that points users to cf. It says it will keep maintaining Wrangler for 18 months after that.

What Cloudflare calls stable

Cloudflare says it expects four things to hold through 1.0: the cloudflare.config.ts config format, the Build Output format that cf build writes and cf deploy reads, the commands that create, develop, build and deploy projects, and the large majority of the API commands used in the beta. The project commands it names are cf init, cf dev, cf build, cf deploy, cf previews deploy and cf workers versions create. Cloudflare says the call path of a small number of less commonly used API commands can still change before 1.0, because cf generates those commands from the Cloudflare API schema.

Checklist of what Cloudflare expects to stay stable in cf 1.0, with a note that a few rarely used API commands can still change
Config, Build Output and the project commands are the parts Cloudflare expects to hold through 1.0.

Live logs

In the beta, Cloudflare’s Wrangler comparison page listed live logs as something cf couldn’t do and told users to run npx wrangler tail. The release candidate adds cf observability tail, which streams live logs and other observability events as newline-delimited JSON.

You pick what to watch with –worker for one Worker, –zone for a zone and its subdomains, or –all for every event in the account. The –filters option narrows the results, as inline JSON or from a file. Worker events only appear if Workers Logs is switched on for that Worker. Long-running commands such as the tail now refresh an expired OAuth login instead of failing.

cf observability tail --worker my-worker
cf observability tail --worker my-worker --filters @filters.json
cf observability tail takes --worker, --zone or --all to pick what to watch, plus --filters to narrow the results
One command now streams live logs for a Worker, a zone or the whole account.

What beta users need to change

Build Output moves to version 1, in .cloudflare/output/v1/, and cf deploy builds again on its first run there. The release candidate needs @cloudflare/vite-plugin 2.0.0-rc.0 or later for projects that build with Vite, and Wrangler 4.163.0 or later for legacy projects that build with Wrangler.

It also renames a few generated API commands without aliases. Cloudflare’s example is cf workers secrets bulk, which is now cf workers secrets bulk-edit. The changelog repeats earlier beta changes for anyone who last updated early on: prompts and progress messages go to stderr, so stdout holds only command output; commands generated from camelCase API names use kebab-case; and cf no longer saves your account choice between runs. Destructive commands run without a terminal exit with an error unless you pass –force.

Build Output moves from v0 to v1, one secrets command is renamed bulk-edit, and Vite and Wrangler have new minimum versions
Beta users get a new Build Output folder, a renamed command and higher minimum versions.

Other beta additions

Since the beta, cf deploy ./dist deploys a directory of static assets as an assets-only Worker. The –temporary-account flag creates a short-lived account without signing in and prints a URL to claim it. Every command accepts –dry-run to preview what it would do, and cf docs search finds Cloudflare documentation from the terminal.

Cloudflare’s changelog doesn’t give a date for 1.0. It asks for bug reports and feedback in the cf repository on GitHub, and the full list of changes is in the CLI release notes.


Discover more from Sulat AI & Tech News

Subscribe to get the latest posts sent to your email.