Cloudflare's New cf CLI Covers 3,000 API Operations, Built for Agents First

Cloudflare released cf on Sept. 28, an open-beta command-line tool that covers more than 3,000 operations across its API and treats an AI agent as the primary user, according to the company's launch post.

The post, written by Matt "TK" Taylor, gives the reason in one number: agents accounted for 48% of Wrangler use last week, up from single digits a year earlier. Wrangler, Cloudflare's existing CLI, has roughly 280 commands.

What cf changes from Wrangler

Cloudflare says the commands are generated from OpenAPI schemas by Forge, a new open-source SDK generator, which is how one tool reaches the whole API.

1. Wrangler (approx.)280 operations
2. cf (minimum)3000 operations

Source: Cloudflare launch post, Sept. 28, 2026 (Wrangler figure given as approximate, cf as more than 3,000)

That breadth creates a discovery problem, so cf ships cf cli search, which lets an agent ask in natural language what it needs to do. Results are matched against API descriptions and parameters.

Output defaults to JSON. The post says: "Agents just need JSON, and if agents are the future primary user of this tool, it should be the default."

Setting	Wrangler	cf
Configuration	TOML or JSONC	cloudflare.config.ts
Dev server and build	esbuild	Vite by default
Install	existing	npm i -g cf

Cloudflare's migration path is cf migrate for existing projects and cf init for new ones. The post says some internal Wrangler configuration files shrank by 40% after the move to TypeScript.

How agents use Wrangler today

The usage data is Cloudflare's own and no outside party has checked it. The post says agents use almost twice as many distinct commands daily and are four times more likely to use six or more commands.

That is Cloudflare's case for a wider command surface. It is also a claim about Wrangler, not about cf, which had been public for one day when the post's figures were read.

The GitHub repository is dual-licensed Apache-2.0 and MIT, had 268 stars and four open issues when checked on Sept. 29, and describes the tool as open beta. The documentation read for this piece mentions no dry-run or confirmation flag for write operations.

What Hacker News objected to

The launch drew 121 points and 51 comments on Hacker News. Several commenters questioned the language. A user named slowin asked why agents would want a TypeScript CLI and raised npm supply-chain exposure; miki123211 said JavaScript's startup time is a problem for command-line tools, and more so for agents.

User hackernud3s said cf cannot create permission tokens, so the first credential still has to be made by hand in the dashboard. User esafak said CI on the repository was failing and that a 1.0 had not shipped. User ozarkerD said the name collides with the Cloud Foundry CLI, which is also invoked as cf.

These are commenters, not audits. The token complaint is the one with the most practical weight, since scoped credentials are the main control on what an agent can change.

Developers weighing where to let an agent run commands may also want the fakecloud AWS emulator covered earlier, and the OpenRig harness for running several agents at once. Cloudflare has not given a date for cf to leave beta.