Reimagining Wrangler CLI and Introducing Local Explorer

Cloudflare's API landscape is vast, with over 100 products and nearly 3,000 HTTP API operations. As developers increasingly use coding agents to interact with these APIs, we aim to make every Cloudflare product accessible across all interfaces agents need, including CLI commands, SDKs, and more. Our focus is on rebuilding the Wrangler CLI to support all Cloudflare products, offering a unified command structure that aligns with infrastructure-as-code practices.

The new Wrangler CLI, currently in technical preview, is designed to provide ergonomic command outputs for both agents and humans. We are developing a new system to generate commands and configurations that keep pace with Cloudflare's rapid product development. This involves rethinking schemas and our code generation pipeline, moving beyond OpenAPI schemas to a new TypeScript schema that defines the full scope of APIs and CLI commands.

Consistency is key for agents using CLIs, so we are establishing rules and guardrails to ensure uniformity across commands. The Wrangler CLI will support both local and remote resources, ensuring consistent defaults and clear outputs to guide agents effectively.

We're also launching Local Explorer, a feature available in open beta, which allows developers to introspect simulated resources locally. This feature supports local development by mirroring the Cloudflare API, enabling developers to manage local resources using the same APIs as remote ones. Local Explorer enhances the local development cycle by providing a simple interface to view and manage data stored locally.

We invite feedback on the technical preview of the Wrangler CLI and encourage developers to share their ideas for future enhancements. Our goal is to create the best possible CLI for Cloudflare's platform, integrating the best aspects of Wrangler with new capabilities. Join us on Cloudflare Developers Discord to contribute your thoughts and stay updated on our progress.