80 /100
Very useful for Cloudflare operations, but deploy and data commands need approval gates.
Structured output 72/100
Whether the CLI can return JSON, YAML, or stable machine-readable output.
Non-interactive use 78/100
Whether common workflows can run predictably without an interactive prompt.
Safety boundaries 60/100
Whether read-only, dry-run, scoped auth, and destructive command boundaries are clear.
Install options
npm
$ npm i -g wrangler Common commands
Check version · safe
$ wrangler --version Confirms the installed CLI.
List deployments · safe
$ wrangler deployments list Inspects recent Worker deployments.
Deploy Worker · requires review
$ wrangler deploy Changes production infrastructure and should be approved.
Agent usage examples
Codex CLI
Use global wrangler for Cloudflare checks. Avoid concurrent wrangler commands and ask before deploy or data mutation. Safety notes
- Read commands such as deployments list and d1 execute SELECT are useful for diagnostics.
- Deploy, KV writes, R2 deletes, and D1 mutation commands should require approval.
- For automation, prefer CLOUDFLARE_API_TOKEN over interactive OAuth.
What agents can use it for
Wrangler helps agents inspect Cloudflare configuration, check deployments, publish Workers, and run bounded D1 or KV operations.
Best fit
Use it for Cloudflare Workers projects where production commands need explicit approval and API-token automation.