This Cloudflare CLI Has 2,900+ Commands for AI [2026]

Cloudflare has started pulling the plug on the command line tool that a generation of Workers developers grew up on. In its place sits cf, a new CLI that the company built less for humans typing commands and more for the AI agents that increasingly type them instead. The tool entered public beta on September 28, 2026, during Cloudflare’s annual Birthday Week event, and by mid October it had become one of the more talked-about release notes in the developer-tools world, covered in detail by InfoQ and debated on Hacker News.

The pitch is simple on its face: one CLI, generated straight from Cloudflare’s own API schemas, that covers nearly the entire Cloudflare product line instead of the narrow slice that Wrangler, the old Workers-focused tool, ever touched. The harder story underneath that pitch is about who the CLI is actually for. Cloudflare has designed cf around the assumption that a coding agent, not a person, will often be the one reading the help text, choosing the command, and parsing the output. That shift says a lot about where developer tooling is heading in late 2026, and it lands at the same moment that coding agents from GitHub Copilot and Cursor are fighting over the same terminal real estate.

Google · Preferred Sources

Don't miss new tech stories on Google

Add TrendinTech once in the Google app and our stories appear in your news suggestions.

Add Now

What the cf CLI Actually Does

Cloudflare’s own product changelog describes cf as a tool that lets developers “manage resources across Cloudflare” through more than 2,900 commands, with most of them returning results as JSON by default. That is not a typo-sized expansion over Wrangler. Wrangler, the CLI that Cloudflare Workers developers have used since the platform’s early days, exposes roughly 280 built-in functions, almost all of them focused on building, testing, and deploying Workers projects. cf instead mirrors Cloudflare’s full public API, generated automatically from the company’s OpenAPI schemas rather than hand-written by individual product teams.

That generation method is the detail that makes cf different from a simple rebrand. Instead of each Cloudflare product team writing its own corner of a CLI, with its own naming conventions and its own quirks, cf is produced directly from the same schema that documents Cloudflare’s REST API. In practical terms, any new Cloudflare API endpoint can show up in cf automatically, without someone on a CLI team needing to hand-code support for it first.

cf vs Wrangler: the Numbers Behind the Switch

The gap between the two tools is wide enough that Cloudflare is treating this as a generational change rather than a point release. The table below lays out the comparison as Cloudflare itself describes it in the product changelog and in Birthday Week materials.

Feature	Wrangler	cf (open beta)
API coverage	About 280 built-in functions, Workers-focused	Over 2,900 commands, generated from Cloudflare’s full OpenAPI schema
Default output	Human-readable tables	JSON-first output across commands
Configuration format	wrangler.jsonc or wrangler.toml	Typed cloudflare.config.ts
Migration path	Not applicable	cf migrate converts a Wrangler config file automatically
Command discovery	Manual lookup via docs or –help	cf cli search accepts a plain-language task description
License	Open source	Open source, Apache License 2.0 or MIT
Status as of October 20, 2026	Active, scheduled for deprecation after beta	Public beta, commands and config can still change

Cloudflare’s own changelog is blunt about the beta caveat: commands, configuration, and build output “can change before the stable release.” Developers building automation against cf today are, by Cloudflare’s own admission, building against a moving target for now.

Why JSON-First Output Matters for Coding Agents

Wrangler, like most developer CLIs built over the last decade, defaults to printing results as readable tables and formatted text, the kind of output a person scans quickly in a terminal. cf flips that default. Every command returns structured JSON unless told otherwise, which is far easier for a coding agent to parse reliably than text formatted for human eyes.

This is not a small implementation detail. Agent-driven coding tools such as Claude Code work by calling command-line tools and reading their output back into a model’s context. When that output is loosely formatted text meant for humans, an agent has to guess at structure, which introduces errors. JSON output removes the guessing. Cloudflare’s documentation goes further, noting that cf commands are designed to describe their own inputs, so an agent can inspect what a command expects before running it rather than relying on a human to have memorized the syntax.

cloudflare.config.ts: TypeScript Replaces TOML and JSONC

The second major break from Wrangler is configuration. Wrangler projects have historically relied on wrangler.toml or, more recently, wrangler.jsonc, both static text formats that describe a Workers project’s settings. cf introduces cloudflare.config.ts, a typed TypeScript configuration file that developers can write programmatically rather than filling out a static template.

Cloudflare built a dedicated migration command for exactly this change. Running cf migrate converts an existing Wrangler configuration file into the new cloudflare.config.ts format automatically, which matters given how many Workers projects currently depend on the older format. The company has not published a complete specification of every option’s TypeScript equivalent, so some manual cleanup after an automated migration should be expected rather than assumed away.

npm install -g cf
cf auth login
cf migrate
cf cli search "deploy a worker with a KV namespace"

cf cli search: How an Agent Finds Commands It Has Never Used

The feature Cloudflare leans on most heavily in its agent-focused messaging is cf cli search. According to Cloudflare’s own changelog, the command “finds the command for a task from a plain-language description, so an agent can find and run commands” without needing to already know the CLI’s exact syntax. That is a meaningful departure from how most CLIs work, where a user, human or automated, either already knows the command or has to search documentation separately.

Cloudflare’s developer documentation also points to a companion feature, cf docs search, which searches Cloudflare’s live documentation directly from the terminal and returns a small set of ranked results in JSON. Put together, the two search commands are meant to let an agent go from a vague instruction, such as “set up a KV namespace for this Worker,” to a concrete, runnable command without a human in the loop translating intent into syntax.

Setting Up cf With Claude Code and Other Coding Agents

Cloudflare has published setup instructions specifically for Claude Code, which involve installing cf globally through npm, authenticating with cf auth login, and then telling Claude Code to prefer the new CLI by noting it in a project’s CLAUDE.md file. Cloudflare positions cf as an alternative to running its Model Context Protocol server for agents that need to reach the Cloudflare API, arguing that a CLI an agent can call directly is simpler to reason about than a separate protocol server running alongside it.

The available documentation confirms this setup path for Claude Code specifically. It does not establish a dedicated, first-party setup guide for Cursor or GitHub Copilot in the same way, though both tools are built to execute arbitrary shell commands, so nothing technically stops them from calling cf the same way a terminal-based agent would. That is a narrower claim than a confirmed native integration, and it is worth treating the two differently when deciding how reliable cf support will be inside a given agent today. Teams already running local coding agents like OpenCode will likely hit the same pattern: shell access is enough to use cf, but a documented, tested integration is a different bar.

Inside Cloudflare’s Birthday Week 2026 Rollout

cf did not launch in isolation. Cloudflare used its 16th Birthday Week, running from September 28 to October 2, 2026, to push out 46 announcements across five themed days, according to the company’s own wrap-up post. Several of those announcements share cf’s agent-first framing, suggesting the CLI is one piece of a broader platform bet rather than a standalone tool.

Announcement	What it does	Status as of October 2026
cf CLI	Agent-oriented CLI covering the full Cloudflare API with JSON output	Open beta
Forge	Open-source pipeline that generates SDKs and documentation from API specs	Released
Cloudflare Containers	Rebuilt container runtime aimed at agent sandboxes	Released
Monetization Gateway	Lets creators charge AI systems for content access using the HTTP 402 status code	Announced
Cloudflare Basin	Data analytics platform	Generally available
K2	Serverless event streaming service	Announced
Workers KV Instant	Key-value storage tier with sub-two-millisecond p99 read latency	Announced

Cloudflare also used the week to confirm plans to operate as a certificate authority and to detail post-quantum cryptography work, alongside EmDash, an open-source serverless content management system built on Astro that runs its plugins inside isolated Worker sandboxes. The common thread across the week, as Cloudflare frames it, is infrastructure built for what the company calls an agent-driven internet, with cf serving as the entry point developers and their agents use to reach almost everything else on that list.

The Wrangler Sunset Timeline

Cloudflare has not framed cf as a tool that will simply coexist with Wrangler indefinitely. The company’s stated plan is to deprecate Wrangler once the cf open beta period ends, ship a final major version of Wrangler that points users toward cf, and then keep Wrangler under maintenance for 18 months to give teams time to migrate. That is a reasonably generous runway by CLI-deprecation standards, but it still puts a clock on every Workers project that has wrangler.toml files, CI pipelines, and internal scripts built around the old tool.

For teams running Workers in production, the practical question is less about whether to move and more about when. cf is explicitly a beta product right now, with Cloudflare warning that commands and configuration can still shift before a stable release. Moving critical deployment pipelines onto a beta CLI the same week it ships is a different risk calculus than moving a side project, and most engineering teams will likely wait for at least one or two stable point releases before retiring Wrangler scripts they depend on.

Developer Reaction: the TypeScript Debate and the Broader Agent Race

Not every reaction has been enthusiastic. Discussion on Hacker News, as covered by InfoQ, raised a specific objection to cf’s choice of TypeScript as its implementation language, with some commenters arguing that compiled languages avoid the dependency management headaches that come with a Node-based CLI people install globally. Cloudflare’s response, relayed in the same coverage, leaned on type safety and language server support as the tradeoff worth making, framing cloudflare.config.ts as a configuration experience that a static file format cannot match.

Cloudflare’s own framing of the rebuild captures the scale of what it was trying to fix. “Wrangler was hand-built with each product team contributing, and we had inconsistent terminology,” the company said in comments reported by InfoQ, adding that the goal with cf was to “standardize what we had and make a massive expansion, all at once.” That is as close as Cloudflare has come to publicly admitting that Wrangler’s patchwork growth, accumulated over years of different teams bolting on their own commands, had become a liability once agents, rather than people, started to be the primary users typing commands into a terminal.

The timing lines up with a broader shift in how developers work. Stack Overflow’s 2025 Developer Survey found that 84 percent of respondents are using or planning to use AI tools in their development process, with 51 percent of professional developers using AI tools daily, according to the 2025 Stack Overflow Developer Survey. The same survey found that only 31 percent of developers are currently using AI agents specifically, a smaller slice than general AI tool usage, which suggests agent-run tooling like cf is being built ahead of where most day-to-day developer habits currently sit rather than in response to an already-mainstream behavior.

Cloudflare cf vs AWS, Google Cloud, Vercel and Supabase CLIs

Cloudflare is not the only infrastructure provider with a command-line tool that developers, and increasingly their agents, rely on. AWS CLI, Google Cloud CLI, Vercel’s CLI, and Supabase’s CLI all predate the current wave of agent-run coding tools and were built primarily around human operators running commands by hand. None of those vendors has published a comparable agent-first redesign on the scale Cloudflare is describing with cf, built from the ground up around JSON-first output, self-describing commands, and natural-language command discovery.

That does not mean rival clouds are standing still. Each of those CLIs already supports JSON output as an option, and all four companies have their own agent and MCP-server efforts underway elsewhere in their platforms. What sets cf apart so far is that Cloudflare built JSON-first behavior, self-describing commands, and command search into the CLI’s defaults rather than offering them as flags a human has to remember to add. Whether AWS, Google Cloud, Vercel, or Supabase follow with their own ground-up rebuilds is the kind of move competitive pressure in developer tooling tends to produce once one major vendor sets a new baseline.

From Hand-Built CLIs to API-Generated Tools: Some History

Wrangler itself is a good example of how most cloud CLIs got built in the first place. It grew alongside Cloudflare Workers, picking up new commands as the Workers platform picked up new features, with different engineering teams adding their own corners of functionality over time. That pattern is common across the industry: a CLI starts narrow, tied to one product, and expands piecemeal as the underlying platform grows, which is exactly how Cloudflare ended up with the inconsistent terminology the company pointed to when explaining cf’s design.

Generating a CLI directly from an OpenAPI schema, as cf does, is a different approach that trades some of that organic, product-team-driven character for consistency and completeness. It is also not unique to Cloudflare in concept, since schema-generated SDKs and clients have existed for years. What is new here is applying that generation approach to a primary developer-facing CLI, at a moment when a growing share of that CLI’s users are software agents rather than people, a shift that tools like VS Code’s recent agent-focused updates and coordination platforms such as BAND are also adapting to in their own ways.

Market Impact for Cloudflare’s Developer Platform

For Cloudflare, cf is less about replacing a CLI and more about keeping its developer platform relevant as a growing share of code gets written, deployed, and debugged by agents rather than people typing directly. If agents are going to be running Workers deployments, managing DNS records, and configuring KV namespaces on a developer’s behalf, Cloudflare has a clear incentive to make sure its own tooling is the easiest, most reliable path for an agent to do that, rather than ceding that ground to a generic MCP server or a third-party wrapper.

The open source license, Apache 2.0 or MIT depending on the component, also lowers the barrier for other agent frameworks to adopt cf conventions or even fork pieces of it, which could extend its influence beyond Cloudflare’s own user base. Whether that bet pays off commercially depends heavily on how quickly agent-run infrastructure management actually becomes common practice rather than an early-adopter pattern, which the Stack Overflow survey data above suggests is still a minority behavior even among developers already comfortable with AI tools generally.

Predictions: What Happens Next for Agent-Ready Tooling

Expect Cloudflare to ship at least one or two more beta point releases before declaring cf stable, given the company’s own warning that commands and configuration can still change.
Wrangler will likely see its usage decline gradually rather than sharply over the 18-month maintenance window, as large production teams wait for cf to prove itself before migrating CI pipelines.
Other major cloud providers are likely to announce their own agent-first CLI efforts within the next year, following the same JSON-first, self-describing command pattern cf has popularized.
Third-party coding agent platforms will probably add documented, tested cf support beyond Claude Code, given how much of the agent coding market now treats Cloudflare Workers as a common deployment target.
Expect continued community debate over the TypeScript-based configuration approach, particularly from teams running cf in minimal container images where Node dependencies carry real weight.

Frequently Asked Questions

What is Cloudflare’s cf CLI?
cf is a new command-line tool from Cloudflare that covers more than 2,900 commands generated directly from the company’s API schemas, with JSON-first output designed to be read reliably by AI coding agents as well as people.

Is cf replacing Wrangler?
Yes. Cloudflare plans to deprecate Wrangler once the cf open beta ends, ship a final Wrangler release pointing users to cf, and keep Wrangler under maintenance for 18 months to give teams time to migrate.

When did cf CLI launch?
cf entered open beta on September 28, 2026, during Cloudflare’s Birthday Week event, and received broader developer-press coverage, including from InfoQ, in October 2026.

How do I migrate my existing Wrangler configuration to cf?
Cloudflare provides a cf migrate command that converts an existing Wrangler configuration file into the new cloudflare.config.ts format automatically, though manual review after migration is advisable since Cloudflare has not published a complete mapping of every option.

Does cf work with Claude Code?
Yes. Cloudflare publishes setup steps for Claude Code specifically, which involve installing cf globally via npm, running cf auth login, and noting a preference for cf in a project’s CLAUDE.md file.

Does cf work with Cursor or GitHub Copilot?
Both tools can execute shell commands, so they can technically call cf, but Cloudflare has not published a dedicated, tested setup guide for either tool the way it has for Claude Code.

Why did Cloudflare default to JSON output instead of readable tables?
Cloudflare built cf around the assumption that AI agents, not just people, will be reading command output, and structured JSON is far easier for an agent to parse reliably than text formatted for human eyes.

Is cf open source?
Yes. Cloudflare has released cf under an open source license, either Apache License 2.0 or MIT depending on the component, and the commands are generated from Cloudflare’s publicly available OpenAPI schemas.

Cloudflare cf CLI Opens 2,900+ Commands to AI Agents [2026]