Half of Wrangler's Users Are Now Agents. Cloudflare Rebuilt the CLI Around Them.
Cloudflare says agents now make up 48% of Wrangler usage, so it shipped a new CLI called cf built for them first. Your internal tools are next in line for the same treatment.
Cloudflare reports that agents accounted for 48% of Wrangler usage in late September, up from a quarter in March 2026 and single digits a year earlier. Its answer is a new CLI, cf, designed around the agent as the primary user and the human as the second.
That number should change how you think about every command-line tool you maintain.
What changed
Wrangler, Cloudflare's existing CLI for Workers, covers about 280 operations. The Cloudflare API offers thousands. Agents like Claude Code and Codex kept hitting that wall, so cf covers more than 3,000.
It is in open beta. Install it with npm i -g cf, then use cf init for a new project or cf migrate to convert an existing Worker.
Cloudflare also measured how agents behave differently. They use almost twice as many distinct commands per day as human users, and are almost four times as likely to use six or more commands.
Wrangler vs cf
| Wrangler | cf | |
|---|---|---|
| API operations covered | About 280 | 3,000+ |
| Config format | Config file | Typed TypeScript (cloudflare.config.ts) |
| Default output | - | JSON, condensed for agents |
| Command discovery | --help | cf cli search, surfaced to agents on first --help |
| Status | Maintenance only after beta ends | Open beta |
Rule: if a tool is going to be driven by an agent, make the machine-readable path the default and the pretty path the option.
Three design choices worth stealing
- Search instead of a giant help page. With thousands of commands,
--helpis useless to a model.cf cli searchtakes a plain-language description and returns matching commands. - Typed config.
cloudflare.config.tsworks with language server plugins in tools like Claude Code and Codex, so the agent gets type errors before it deploys, not after. - JSON by default. Agents parse output. Humans get pretty-printed output.
The caveats
Wrangler is not going away overnight. cf migrate converts Workers built with Vite. Workers that use esbuild, plus Rust and Python Workers, stay on Wrangler for builds, dev, and deploy. When the beta ends, a final major Wrangler release will point users and agents to cf, followed by 18 months of maintenance support.
Beta means beta. Pin versions in CI and keep Wrangler as your fallback until cf covers your stack.
What to do with this
If you run an internal platform team, check your own CLI logs. Count how many invocations come from agent sessions. If the share is anywhere near 48%, your docs, error messages, and help output are being read mostly by models.
Fix them for that reader first. The humans will benefit too.
Found this helpful? Share it with others!