# Wrangler

> Cloudflare Wrangler CLI: Workers, KV, R2, D1, tail, deploy, account routing.

- Skill: `mouadja02/wrangler` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mouadja02/wrangler`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mouadja02/wrangler/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: mouadja02 (https://skillmd.com/u/mouadja02)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mouadja02/wrangler

---


# Wrangler

> **Attribution:** Sourced from [steipete/agent-scripts](https://github.com/steipete/agent-scripts) by [Peter Steinberger](https://github.com/steipete).

## When to Use

- Deploying or tailing Cloudflare Workers
- Managing KV namespaces, R2 buckets, D1 databases, or Queues via CLI
- Debugging Wrangler account routing or deploy failures

Use for Cloudflare Wrangler CLI work: deploys, tails, KV/R2/D1/Queues/Workers, secrets, bindings, and account routing.

## Defaults

- Retrieval first for flags/config: `wrangler --help`, subcommand `--help`, local `node_modules/wrangler/config-schema.json`, then Cloudflare docs.
- Prefer repo wrapper: `npm exec --yes --package wrangler -- wrangler ...` unless repo has its own script.
- `wrangler whoami` before account-sensitive work.

## Quick Commands

```bash
# Check auth
npm exec --yes --package wrangler -- wrangler whoami

# Deploy
npm exec --yes --package wrangler -- wrangler deploy

# Tail logs
npm exec --yes --package wrangler -- wrangler tail <worker> --format json --sampling-rate 0.999 --search '<term>'

# KV operations
npm exec --yes --package wrangler -- wrangler kv key list --namespace-id <id> --prefix '<prefix>'
npm exec --yes --package wrangler -- wrangler kv key get '<key>' --namespace-id <id>
```

## Pitfalls

- Do not invent flags from memory. Wrangler 4 removed/changed some old flags; confirm with `--help`.
- `wrangler kv key list` has no `--limit`; use `--prefix` and filter locally.
- Run Wrangler KV/list/get/admin reads serially when workerd/local storage starts up; parallel runs can hit SQLite `SQLITE_BUSY`.
- `wrangler tail --sampling-rate` must be `>0` and `<1`; use `0.999` for near-full sampling, not `1`.
- Stop tails you start. Kill the exact `wrangler tail <worker>` process when done.
- Never print secrets. Query exact secret names only; do not dump env.

## Account Check

For repo config, read `wrangler.toml` / `wrangler.json` before commands. If config account and intended product disagree, stop and ask.

```bash
cat wrangler.toml | grep -E "account_id|name ="
npm exec --yes --package wrangler -- wrangler whoami
```