Cloudflare launches cf, an agentic CLI covering its entire 3,000-operation API
- Cloudflare launched cf in open beta, a CLI that covers the whole Cloudflare API surface of more than 3,000 operations, up from the roughly 280 commands Wrangler accumulated, with commands generated from OpenAPI schemas through Cloudflare's Forge pipeline.
- Agents accounted for 48% of Wrangler usage last week, up from single digits a year earlier and a quarter in March 2026; they run almost twice as many distinct commands per day and are nearly four times as likely to use six or more commands.
- JSON is the default output, pretty printed for humans and condensed for agents, and the new cloudflare.config.ts TypeScript config starts with Workers and extends to all of Cloudflare, with Vite as the default local dev server.
- Cloudflare chose a brand new CLI instead of reworking Wrangler because years of docs, blogs and third-party guides are baked into LLM training, so an agent contextualizing two versions of a familiar tool is more confusing than learning a fresh one.
Hacker News opinions
the cf cli search is the part I actually want. I've had better luck having agents write bash scripts around a tool than handing them markdown docs they follow half the time, and keeping credentials out of the agent's process kills a whole class of problems.
if you're going to modify cloud infra, keep doing IaC. The CLI is great for read-only debug sessions.
you linked to the questionnaire skill, did you mean the wizard one?
the shape of clouds is going to change now that agents are the users. Cloudflare is making the right bet, and the free agent report account is a genuinely nice idea for agent sharing.
as someone who basically only touches the Cloudflare API through agents, there's a lot to like. Since this is built on Forge, I hope native terraform output is coming, great for a solo dev deploying a worker but huge for production if it can emit terraform.
no idea what it was about wrangler that made me hate it, but I welcome anything meant to replace it.
my biggest wrangler gripe was the inconsistency between dev and prod.
cool, but agents already handle Cloudflare fine by just making REST calls with the docs. Is the CLI a subset of that or does it cover everything?
the real title is 'the agentic CLI for the entire Cloudflare API'. That word is doing all the work and it's missing from the HN title.
why is this written in TypeScript? Don't make users manage your CLI's dependencies, write it in a compiled language and tell your agents to pick the right architecture.
you think the TypeScript choice wasn't deliberate? It makes total sense inside Cloudflare's existing tooling.
it's usually whichever team got assigned the product that picks the stack. When you see TypeScript in a TUI or CLI, it's reusing the skill set of that team, and the TypeScript people at Cloudflare are probably on bigger problems.
AWS and GCP CLIs have been Python for a decade. Python isn't compiled either.
so tell Claude to rewrite it in amd64 and arm64 assembly and formally verify it while it's at it.
it's the modern big-tech mode: optimize the hell out of it in Rust when it runs on your own infrastructure, go with JS/TS/Electron when it runs on users' machines.
1.0 isn't actually out and CI is red. I've had success with the pre-releases but this post could have waited a few days.
it's wild that some of the best product launches right now are CLIs.
agreed, Cloudflare is shipping really well lately.
great, now I have to uninstall the Cloudfoundry CLI so the names don't collide.
make single letter aliases, c=cf, g=git, works fine.