Introducing cf: the agentic CLI for the entire Cloudflare API
- ID
- 29330
- Status
- summarized
- Published
- 28 Sep 2026, 11:50 PM
- Fetched
- 29 Sep 2026, 8:45 PM
- Provider
- Cloudflare Blog
- Category
- infrastructure
- Original URL
- https://blog.cloudflare.com/cloudflare-cf-cli-launch/
- Source URL
- https://blog.cloudflare.com/rss/
Summary
- Score
- 7.0
- Created
- 29 Sep 2026, 8:46 PM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Cloudflare launched `cf`, an open beta CLI (npm i -g cf) that exposes the entire Cloudflare API rather than the ~280 Wrangler command paths. It defaults to JSON output — pretty-printed for humans, condensed for agents — adds a `cloudflare.config.ts` TypeScript config starting with Workers, and makes Vite the default local dev server. Cloudflare reports agent usage of Wrangler hit 48% last week, up from ~25% in March 2026 and single digits the year before, with agents running roughly twice as many distinct commands per day. Existing Wrangler projects (wrangler.jsonc/json/toml) stay on Wrangler unless migrated via `cf migrate`.
Why it matters
If you or your agents drive Cloudflare from scripts, the decision is now explicit: keep Wrangler in repos that have a wrangler.jsonc/json/toml file, or run `cf migrate` and adopt cloudflare.config.ts. New agents should be pointed at `cf` with `cf --help` or `cf cli search` instead of guessing Wrangler syntax — Cloudflare's own guidance says a failing `cf` command should not silently fall back to `npx wrangler`. The 48% agent-usage figure is also a concrete datapoint if you are deciding whether to optimize your own CLI or API output for agent consumers rather than humans.
Discussion angle
Cloudflare says agents are now ~48% of Wrangler usage and run about twice as many distinct commands as humans — is that enough reason to design your own tool's default output as condensed JSON for agents, and where does that hurt human debugging?