Wrangler CLI

CLI for deploying and managing Cloudflare Workers, KV, R2, D1, Vectorize, Hyperdrive, AI, Containers, Queues, Workflows, and Pipelines.

- Covers 10+ resource types with dedicated commands for creation, configuration, and lifecycle management across Workers, storage, databases, and compute services

- Supports local development with wrangler dev using local storage simulation or remote bindings for real resources; includes TypeScript type generation via wrangler types

- Configuration via wrangler.jsonc with support for environment-specific overrides, secrets management, cron triggers, and Durable Objects bindings

- Provides deployment workflows including dry-run validation, versioning, rollback, and secret management; tail command for live log streaming

Wrangler CLI

Your knowledge of Wrangler CLI flags, config fields, and subcommands may be outdated. Prefer retrieval over pre-training for any Wrangler task.

Retrieval Sources

Fetch the latest information before writing or reviewing Wrangler commands and config. Do not rely on baked-in knowledge for CLI flags, config fields, or binding shapes.

Source
How to retrieve
Use for

Wrangler docs
https://developers.cloudflare.com/workers/wrangler/
CLI commands, flags, config reference

Wrangler config schema
node_modules/wrangler/config-schema.json
Config fields, binding shapes, allowed values

Cloudflare docs
Search tool or https://developers.cloudflare.com/workers/
API reference, compatibility dates/flags

FIRST: Check if Wrangler is installed, and if not, install it

Check if Wrangler is installed by running: