wrangler

# Wrangler CLI Use the project's Wrangler version and retrieve the relevant documentation before writing commands or configuration. CLI flags and configuration fields change; do not rely on memorized examples. ## Inspect the Project - Find the package manager, installed Wrangler version, package scripts, framework, and Wrangler config. Run commands through the project's scripts or package manager so they use its local version. Install dependencies using the existing lockfile when needed; do not silently upgrade Wrangler to match current docs. If Wrangler is not a dependency, follow the [installation guide](https://developers.cloudflare.com/workers/wrangler/install-and-update/) to add it locally. - Identify the config used by the build or deploy command, including framework-generated config. Edit its source rather than generated output. - Establish the target account, Worker, environment, and resource before running commands that change them. For data operations, determine whether the target is local or remote. ## Retrieve What the Task Needs Use the Cloudflare MCP `docs` tool if available, or fetch the relevant linked page directly. Follow links to the specific command or product involved; avoid loading the entire reference. If a page moves, rediscover it through the [Wrangler command index](https://developers.cloudflare.com/workers/wrangler/commands/) or Cloudflare docs search. | Task | Source | | --- | --- | | Discover commands and flags, including resource management...