What changed
On September 28, Cloudflare released the open-beta cf CLI. Unlike Wrangler, whose commands were hand-built across product teams, cf is generated through Cloudflare’s Forge API pipeline and is intended to expose the whole Cloudflare API through one consistent command surface. Cloudflare says this takes coverage from roughly 280 Wrangler command paths to more than 3,000 API operations.
Why it matters
Coding agents increasingly operate infrastructure directly, but traditional CLIs often expose inconsistent verbs, human-oriented tables and only a subset of a platform. cf makes the agent the primary CLI consumer: machine-readable output is the default, command discovery is built in, and typed configuration gives language-server-aware agents more context before they edit infrastructure.
The CLI is generated from the API rather than hand-built product by product
Cloudflare says Forge uses the OpenAPI schema behind its documentation and SDKs to generate CLI commands. That changes the maintenance model: new API operations can fit a common command structure instead of waiting for bespoke Wrangler support.
The interface assumes an agent is the main user
cf defaults to JSON and includes command search because an agent may need to discover one operation among thousands without loading the entire command catalogue into context. Human-interactive forms remain available for operations that require structured input.
Wrangler is not disappearing immediately
The release is an open beta. Cloudflare says Wrangler will receive a final major version after the beta and then 18 months of maintenance support, giving existing Workers projects a migration window rather than forcing an immediate switch.