SYSTEM Cited by 1 source

cf CLI (next-generation Wrangler, Technical Preview)¶

cf is the Technical Preview of the next-generation Wrangler CLI — a single command-line tool intended to expose every one of Cloudflare's 100+ products and ~3,000 HTTP API operations through one consistent, agent-ergonomic interface. Installable today via npx cf or npm install -g cf (Source: sources/2026-04-13-cloudflare-building-a-cli-for-all-of-cloudflare).

Why it exists¶

Today's Wrangler covers only some Cloudflare products. Many products have no CLI commands, which is a usability problem for humans and a blocker for AI agents — "agents love CLIs". And increasingly, agents are the primary customer of Cloudflare APIs, so the CLI must be built for them first.

Rebuilding Wrangler to cover everything in sync with Cloudflare's rapid product development required a new code-generation pipeline and a new schema format — see concepts/unified-interface-schema and patterns/schema-driven-interface-generation.

What the preview ships today¶

npx cf / npm install -g cf install flow.
A small subset of Cloudflare products is covered at preview time; internally Cloudflare is already testing a build that covers the entire API surface.
Consistency guardrails baked into the schema:
Always get, never info.
Always --force, never --skip-confirmations.
Always --json, never --format (and --json supported on every command that has structured output).
Local / remote parity: --local flag routes the command to a local mirror of the Cloudflare API provided by Local Explorer; every other flag and argument is identical between local and remote.
Output format ergonomic for both agents and humans — clearly signals whether commands ran against remote or local resources.

See concepts/cli-convention-enforcement for why these rules are enforced in the schema, not in code review.

Relation to the existing Wrangler¶

This is the Technical Preview of what the next Wrangler will become. Over the coming months, Cloudflare will merge this new cf binary with the parts of existing Wrangler that developers rely on (wrangler dev, wrangler deploy, bindings, wrangler.jsonc configuration, etc.) into a single tool. The rename from wrangler to cf signals "CLI for all of Cloudflare" rather than "CLI for Workers".

Generated from one TypeScript schema¶

cf commands, their arguments, their wrangler.jsonc configuration options, the Workers Bindings RPC APIs, the Cloudflare SDKs across languages, the Terraform provider, the MCP Code Mode server, and the Agent Skills are all generated from one internal TypeScript schema. OpenAPI is an output of this schema, not an input. See patterns/typescript-as-codegen-source and patterns/schema-driven-interface-generation.

Agent ergonomics¶

--json everywhere, structured output that parses.
Consistent verbs (get / list / create / delete), so an agent that learned the pattern for one product can try the same pattern on any other product and have it exist.
Local / remote explicitly flagged in output — closes a class of agent failures where the agent writes to local thinking it's remote (or vice-versa) and then can't reconcile the state.
CLI is one of several interfaces exposed to agents; the others include MCP Code Mode (all 3,000 operations in <1,000 tokens), Workers Bindings, and SDK surfaces.

Feedback channel¶

Cloudflare is explicitly building cf in public; the Developers Discord is the feedback channel. The post asks:

What commands do you wish existed?
What do you want to configure in wrangler.jsonc that currently requires dashboard clicks (DNS records, Cache Rules)?
Where do your agents get stuck, and what CLI commands would unstick them?

Caveats¶

Technical Preview only — small subset of products covered today.
No committed GA date.
The TypeScript schema format itself is not open-source as of this post.

Seen in¶

sources/2026-04-13-cloudflare-building-a-cli-for-all-of-cloudflare — launch post.