Cloudflare just said the quiet part out loud: agents are now the primary customer of their APIs. To back that up, they're rebuilding Wrangler, their CLI tool, under the new name "cf." The technical preview runs via `npx cf` and aims to cover all 100-plus Cloudflare products and nearly 3,000 API operations. Right now it only supports a small subset, but Cloudflare is already testing an internal version with full API coverage.
What matters is how they built it. Cloudflare created a custom TypeScript-based schema system that generates commands, configuration, SDKs, docs, and Agent Skills from a single source of truth. OpenAPI schemas weren't enough because they only describe REST APIs. Cloudflare needed something that could also handle interactive CLI commands, Workers bindings, and the documentation tying everything together. This schema enforces consistency at a structural level, which matters enormously for AI agents. If one command uses "info" and another uses "get" for the same operation, an agent will fail. So they built guardrails directly into the schema. It's always "get," never "info." Always "--force," never "--skip-confirmations."
They're also launching Local Explorer, which lets developers introspect simulated local resources like KV, R2, D1, and Durable Objects through a local API mirror. Previously, figuring out what data was stored locally meant digging through the .wrangler/state directory or installing third-party tools. Now you press "e" during local development to see what your Worker's bindings contain. For agent builders, that's a direct window into what your AI is doing with your data before anything ships.