Cloudflare has launched the open beta of cf, a new open-source command-line interface aimed at AI agents and developers working with Cloudflare services. The company says the new tool is meant to replace Wrangler over time, with a final major Wrangler release, 18 months of maintenance support, and a migration path to the new CLI.
Why Cloudflare is moving beyond Wrangler
Cloudflare says cf was built to avoid the compatibility constraints of Wrangler and to better match how AI agents interact with tools. The company argues that Wrangler had grown unevenly over time, with different product teams contributing their own command patterns and terminology.
In the words of Matt Taylor, senior product manager at Cloudflare, and Samuel Macleod, senior systems engineer at Cloudflare, Wrangler had been “hand-built” across teams, which made it difficult to enforce consistent patterns across its roughly 280 command paths. They pointed to inconsistent naming such as d1 info, hyperdrive get, and workflows describe as examples of the tool’s fragmented evolution.
Cloudflare says creating a new CLI allowed it to standardize the developer experience while also redesigning the interface for agent-driven workflows.
What cf is designed to do
The new CLI is written in TypeScript and released under either the Apache License 2.0 or MIT license. Cloudflare says it offers structured command discovery, JSON output optimized for both humans and agents, and a new cloudflare.config.ts configuration format.
It also makes Vite the default development environment, which Cloudflare says provides a more consistent local development setup and plugin support. The company presents these changes as part of a broader effort to make Cloudflare services easier to use programmatically, especially in workflows where AI systems need to inspect and modify configuration.
More than a CLI refresh
Cloudflare says cf is not simply a rebrand of Wrangler. Instead, it is intended as a more agent-aware interface that favors machine-readable output and discoverable commands over older conventions built primarily for human terminal users.
That emphasis is reflected in the defaults: JSON comes first, and table views are something users must request explicitly. Cloudflare says this makes the output easier for agents to parse and transform, while still allowing humans to view formatted tables when needed.
Built from Cloudflare’s API schemas
One of the most significant changes is the scale of coverage. Cloudflare says cf is generated from its OpenAPI schemas and can cover more than 3,000 API operations, compared with roughly 280 functions in Wrangler.
Taylor and Macleod said the company wanted to “standardize what we had and make a massive expansion” at the same time. They added that Forge, Cloudflare’s new unified API generation pipeline, made that possible by generating CLI commands directly from the API schema used for documentation and SDK generation.
That approach lets Cloudflare expand the tool without relying on the older hand-built command structure that shaped Wrangler. It also aligns the CLI more closely with the same source of truth used across the company’s API tooling.
TypeScript sparks debate
Community reaction has focused heavily on Cloudflare’s choice to write a CLI in TypeScript. In a widely discussed Hacker News thread, commenters raised concerns about startup time, portability, and dependency management.
One user, slowin, argued that a CLI should be written in a compiled language and warned against forcing users to manage dependencies. The comment also questioned why a tool for AI-assisted coding would itself be written in TypeScript.
Cloudflare’s response is that TypeScript brings practical benefits for both humans and agents. The company says type safety and language server support help users and tools understand configuration more accurately, while programmatic configuration can reduce duplication.
Cloudflare also contrasted cloudflare.config.ts with TOML and JSONC, arguing that those formats make schema information less accessible to agents. In its view, a typed configuration file is better suited to machine-assisted workflows.
JSON first, tables second
The default output format is another deliberate shift. Ashish Ganda summarized the philosophy on LinkedIn by saying that Cloudflare’s new CLI outputs JSON by default, not tables, adding: “Tables are for eyes. JSON is for parsers.”
Cloudflare appears to agree. Its position is that agents can filter and reshape JSON into whatever format a human user needs, while still preserving the underlying structure for automation. That design choice underscores the company’s broader pitch: cf is meant to work as a tool for both people and software agents, but with machine consumption as the primary default.
What happens to Wrangler
Cloudflare says Wrangler will not disappear immediately. The company plans to deprecate it after the cf open beta ends, then ship one final major Wrangler version that directs users to the new CLI.
After that, Cloudflare intends to provide 18 months of maintenance support to give teams time to migrate. That should give existing users a defined transition window, especially for organizations that depend on Wrangler in production workflows.
For now, the open beta gives Cloudflare a chance to test whether a CLI built for AI agents can also become the preferred tool for human developers. If adoption follows the company’s expectations, cf may become one of the clearest examples yet of infrastructure software being reshaped around agentic development.
Source: Original report
Was this helpful?
Explore more: Software Development More Software Development Tech News
Last Modified: October 6, 2026 at 10:33 pm
0 views
