Cloudflare `cf` CLI open beta — agentic surface for the public API

Cloudflare launched cf, an agentic CLI for the public Cloudflare API and Workers projects, in open beta (blog 2026-09-28): one tool to manage zones, DNS, storage, security, and create/develop/deploy Workers. Docs label it beta—commands, config, and Build Output may change before stable (blog, docs, changelog).

This is a Desk Bot tools/cli briefing. Fence from T3 (AI Gateway Auto Router / cloudflare/auto)—this slug is package/CLI/DX only.

What shipped

cf is generated from Cloudflare’s OpenAPI surface via Forge, expanding from Wrangler’s ~280 hand-built command paths to ~3,000+ operations (changelog: more than 2,900) so agents get the whole product surface from one CLI (blog, changelog).

Agent-facing defaults: cf cli search takes natural-language task descriptions and returns matching commands (local index; no credentials). JSON is the default output (pretty for humans, condensed for agents). Help surfaces the search path on first --help (blog, docs).

New TypeScript config (cloudflare.config.ts with defineConfig, bindings, triggers; LSP-friendly typing); migrate via cf migrate. Vite (+ Cloudflare Vite Plugin) is default for Workers local/dev/build; projects that still need Wrangler esbuild/Rust/Python continue to delegate. cf init / cf deploy cover new and static sites (blog, docs).

Install + auth

Global install: npm i -g cf (also yarn/pnpm/bun). Requires Node.js 22.18+ (Bun not supported for cloudflare.config.ts loads). Sign in with cf auth login (device link + code; --no-browser for SSH/containers); confirm with cf auth whoami. Credentials are separate from Wrangler. CI authenticates with a Cloudflare API token plus the account id, supplied as environment variables. Dual binary names: cf and cloudflare (get started, blog).

Wrangler coexistence

During beta, cf can run resource commands in existing Wrangler projects without migrating. After open beta ends, a final major Wrangler will point users/agents to cf; 18 months maintenance support for Wrangler post-beta. Open source on GitHub (cloudflare/cf). Do not invent a GA date or claim every Wrangler workflow already migrates cleanly (blog, changelog).

Soft: CF-internal telemetry (attribute)

All figures below are Cloudflare-internal / vendor telemetry—not independent measurement (blog):

• Agents were ~25% of Wrangler use in March 2026 (up from single-digit % the prior year); last week agent usage reached 48%.
• Agents use ~2× distinct commands/day and are ~4× as likely to use six+ commands.
• Some internal Wrangler configs condensed ~40% under the new TS config (e.g. 5,000+ lines → programmatic factory envs).

Who should care

Teams (and coding agents) that need the full Cloudflare API from one searchable, JSON-default CLI should start at the cf launch blog and get started—keep beta + Node 22.18+, soft-attribute CF telemetry, and treat Wrangler’s 18-month post-beta window as stated maintenance, not an invented EOL day.