Cloudflare has introduced cf, a next-generation command-line interface designed to expose the entire Cloudflare API surface to developers and agentic tooling. The tool replaces previous fragmented CLIs by unifying thousands of API operations under a consistent, JSON-first interface optimized for automation and agent workflows.
- Expands CLI coverage from ~280 to 3,000+ Cloudflare API operations
- Built for agent and automation-first workflows with uniform JSON output
- Standardizes developer experience and command patterns across teams
Infrastructure signal
The launch of the cf CLI reflects Cloudflare’s move towards a more unified and scalable interface for infrastructure management across its extensive product ecosystem. Rather than fragmented tooling with limited command sets, cf unlocks access to Cloudflare’s full API catalog, enhancing cloud management capabilities from deployment to security configurations.
This broad coverage reduces reliance on team-specific, custom-built CLIs, enabling smoother integration with automation and CI/CD pipelines. It also supports more consistent observability and monitoring through structured JSON outputs designed specifically for machine consumption rather than human-readable terminals.
Developer impact
For developers, cf represents a streamlined workflow where countless manual steps—deploying workers, configuring access, setting up WAF rules—can be scripted and automated within a single CLI context. The unified API surface ensures that learning curve and command discoverability are greatly improved, fostering faster iteration cycles.
Because cf is generated directly from the annotated OpenAPI schemas via Forge, the developer experience gains from consistency in terminology, standard command patterns, and integrated documentation. This reduces friction that previously arose from disparate tools, inconsistent naming, and varied output formats.
What teams should watch
Teams managing Cloudflare infrastructure should anticipate a phased migration from Wrangler and other fragmented CLIs to cf, especially as agent usage continues to dominate within organizational workflows. They should prepare to update automation scripts and observability setups to consume cf’s JSON outputs and leverage its expanded command set.
Additionally, developer and operations teams should monitor the ongoing evolution of cf’s agentic features, which promise new paradigms for command discovery and contextual assistance tailored to autonomous and semi-autonomous development agents. Embracing cf early will position teams to leverage Cloudflare’s platform more effectively as their infrastructure scales.