Building a CLI for All of Cloudflare

Cloudflare is rebuilding the Wrangler CLI to support its entire product suite and optimize for AI agents. Additionally, the new Local Explorer feature has been introduced to bridge the gap between local and cloud development environments.
Cloudflare has a vast API surface. We have over 100 products, and nearly 3,000 HTTP API operations. Increasingly, agents are the primary customer of our APIs. Developers bring their coding agents to build and deploy applications, agents, and platforms to Cloudflare, configure their account, and query our APIs for analytics and logs. We want to make every Cloudflare product available in all of the ways agents need. Today, many of our products aren’t available across every one of these interfaces. This is particularly true of our CLI — Wrangler. So we’ve been rebuilding Wrangler CLI, to make it the CLI for all of Cloudflare. Today we’re sharing an early version of what the next version of Wrangler will look like as a technical preview. You can try the Technical Preview today by running npx cf. To build this in a way that keeps in sync with the rapid pace of product development, we had to create a new system that allows us to generate commands, configuration, binding APIs, and more based on a new TypeScript schema. One of the first things we’ve done is to start creating rules and guardrails, enforced at the schema layer to ensure consistency for agents. Today we are also releasing Local Explorer, a new feature available in open beta in both Wrangler and the Cloudflare Vite plugin. Local Explorer lets you introspect the simulated resources that your Worker uses when you are developing locally, including KV, R2, D1, Durable Objects and Workflows. Our goal here is to provide a mirror of the Cloudflare API that only modifies local data, so that all of your local resources are available via the same APIs that you use remotely.
Source: Hacker News
















