Auto-Pilot
Updated a month ago

wrangler

Ccloudflare
0.1k
cloudflare/skills/wrangler
72
Agent Score

💡 Summary

English summary.

🎯 Target Audience

Persona 1Persona 2Persona 3

🤖 AI Roast:Powerful, but the setup might scare off the impatient.

Security AnalysisMedium Risk

Risk: Medium. Review: shell/CLI command execution; outbound network access (SSRF, data egress); API keys/tokens handling and storage; filesystem read/write scope and path traversal; dependency pinning and supply-chain risk. Run with least privilege and audit before enabling in production.


name: wrangler description: Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices.

Wrangler CLI

Deploy, develop, and manage Cloudflare Workers and associated resources.

FIRST: Verify Wrangler Installation

wrangler --version # Requires v4.x+

If not installed:

npm install -D wrangler@latest

Key Guidelines

  • Use wrangler.jsonc: Prefer JSON config over TOML. Newer features are JSON-only.
  • Set compatibility_date: Use a recent date (within 30 days). Check https://developers.cloudflare.com/workers/configuration/compatibility-dates/
  • Generate types after config changes: Run wrangler types to update TypeScript bindings.
  • Local dev defaults to local storage: Bindings use local simulation unless remote: true.
  • Validate config before deploy: Run wrangler check to catch errors early.
  • Use environments for staging/prod: Define env.staging and env.production in config.

Quick Start: New Worker

# Initialize new project npx wrangler init my-worker # Or with a framework npx create-cloudflare@latest my-app

Quick Reference: Core Commands

| Task | Command | |------|---------| | Start local dev server | wrangler dev | | Deploy to Cloudflare | wrangler deploy | | Deploy dry run | wrangler deploy --dry-run | | Generate TypeScript types | wrangler types | | Validate configuration | wrangler check | | View live logs | wrangler tail | | Delete Worker | wrangler delete | | Auth status | wrangler whoami |


Configuration (wrangler.jsonc)

Minimal Config

{ "$schema": "./node_modules/wrangler/config-schema.json", "name": "my-worker", "main": "src/index.ts", "compatibility_date": "2026-01-01" }

Full Config with Bindings

{ "$schema": "./node_modules/wrangler/config-schema.json", "name": "my-worker", "main": "src/index.ts", "compatibility_date": "2026-01-01", "compatibility_flags": ["nodejs_compat_v2"], // Environment variables "vars": { "ENVIRONMENT": "production" }, // KV Namespace "kv_namespaces": [ { "binding": "KV", "id": "<KV_NAMESPACE_ID>" } ], // R2 Bucket "r2_buckets": [ { "binding": "BUCKET", "bucket_name": "my-bucket" } ], // D1 Database "d1_databases": [ { "binding": "DB", "database_name": "my-db", "database_id": "<DB_ID>" } ], // Workers AI (always remote) "ai": { "binding": "AI" }, // Vectorize "vectorize": [ { "binding": "VECTOR_INDEX", "index_name": "my-index" } ], // Hyperdrive "hyperdrive": [ { "binding": "HYPERDRIVE", "id": "<HYPERDRIVE_ID>" } ], // Durable Objects "durable_objects": { "bindings": [ { "name": "COUNTER", "class_name": "Counter" } ] }, // Cron triggers "triggers": { "crons": ["0 * * * *"] }, // Environments "env": { "staging": { "name": "my-worker-staging", "vars": { "ENVIRONMENT": "staging" } } } }

Generate Types from Config

# Generate worker-configuration.d.ts wrangler types # Custom output path wrangler types ./src/env.d.ts # Check types are up to date (CI) wrangler types --check

Local Development

Start Dev Server

# Local mode (default) - uses local storage simulation wrangler dev # With specific environment wrangler dev --env staging # Force local-only (disable remote bindings) wrangler dev --local # Remote mode - runs on Cloudflare edge (legacy) wrangler dev --remote # Custom port wrangler dev --port 8787 # Live reload for HTML changes wrangler dev --live-reload # Test scheduled/cron handlers wrangler dev --test-scheduled # Then visit: http://localhost:8787/__scheduled

Remote Bindings for Local Dev

Use remote: true in binding config to connect to real resources while running locally:

{ "r2_buckets": [ { "binding": "BUCKET", "bucket_name": "my-bucket", "remote": true } ], "ai": { "binding": "AI", "remote": true }, "vectorize": [ { "binding": "INDEX", "index_name": "my-index", "remote": true } ] }

Recommended remote bindings: AI (required), Vectorize, Browser Rendering, mTLS, Images.

Local Secrets

Create .dev.vars for local development secrets:

API_KEY=local-dev-key
DATABASE_URL=postgres://localhost:5432/dev

Deployment

Deploy Worker

# Deploy to production wrangler deploy # Deploy specific environment wrangler deploy --env staging # Dry run (validate without deploying) wrangler deploy --dry-run # Keep dashboard-set variables wrangler deploy --keep-vars # Minify code wrangler deploy --minify

Manage Secrets

# Set secret interactively wrangler secret put API_KEY # Set from stdin echo "secret-value" | wrangler secret put API_KEY # List secrets wrangler secret list # Delete secret wrangler secret delete API_KEY # Bulk secrets from JSON file wrangler secret bulk secrets.json

Versions and Rollback

# List recent versions wrangler versions list # View specific version wrangler versions view <VERSION_ID> # Rollback to previous version wrangler rollback # Rollback to specific version wrangler rollback <VERSION_ID>

KV (Key-Value Store)

Manage Namespaces

# Create namespace wrangler kv namespace create MY_KV # List namespaces wrangler kv namespace list # Delete namespace wrangler kv namespace delete --namespace-id <ID>

Manage Keys

# Put value wrangler kv key put --namespace-id <ID> "key" "value" # Put with expiration (seconds) wrangler kv key put --namespace-id <ID> "key" "value" --expiration-ttl 3600 # Get value wrangler kv key get --namespace-id <ID> "key" # List keys wrangler kv key list --namespace-id <ID> # Delete key wrangler kv key delete --namespace-id <ID> "key" # Bulk put from JSON wrangler kv bulk put --namespace-id <ID> data.json

Config Binding

{ "kv_namespaces": [ { "binding": "CACHE", "id": "<NAMESPACE_ID>" } ] }

R2 (Object Storage)

Manage Buckets

# Create bucket wrangler r2 bucket create my-bucket # Create with location hint wrangler r2 bucket create my-bucket --location wnam # List buckets wrangler r2 bucket list # Get bucket info wrangler r2 bucket info my-bucket # Delete bucket wrangler r2 bucket delete my-bucket

Manage Objects

# Upload object wrangler r2 object put my-bucket/path/file.txt --file ./local-file.txt # Download object wrangler r2 object get my-bucket/path/file.txt # Delete object wrangler r2 object delete my-bucket/path/file.txt

Config Binding

{ "r2_buckets": [ { "binding": "ASSETS", "bucket_name": "my-bucket" } ] }

D1 (SQL Database)

Manage Databases

# Create database wrangler d1 create my-database # Create with location wrangler d1 create my-database --location wnam # List databases wrangler d1 list # Get database info wrangler d1 info my-database # Delete database wrangler d1 delete my-database

Execute SQL

# Execute SQL command (remote) wrangler d1 execute my-database --remote --command "SELECT * FROM users" # Execute SQL file (remote) wrangler d1 execute my-database --remote --file ./schema.sql # Execute locally wrangler d1 execute my-database --local --command "SELECT * FROM users"

Migrations

# Create migration wrangler d1 migrations create my-database create_users_table # List pending migrations wrangler d1 migrations list my-database --local # Apply migrations locally wrangler d1 migrations apply my-database --local # Apply migrations to remote wrangler d1 migrations apply my-database --remote

Export/Backup

# Export schema and data wrangler d1 export my-database --remote --output backup.sql # Export schema only wrangler d1 export my-database --remote --output schema.sql --no-data

Config Binding

{ "d1_databases": [ { "binding": "DB", "database_name": "my-database", "database_id": "<DATABASE_ID>", "migrations_dir": "./migrations" } ] }

Vectorize (Vector Database)

Manage Indexes

# Create index with dimensions wrangler vectorize create my-index --dimensions 768 --metric cosine # Create with preset (auto-configures dimensions/metric) wrangler vectorize create my-index --preset @cf/baai/bge-base-en-v1.5 # List indexes wrangler vectorize list # Get index info wrangler vectorize get my-index # Delete index wrangler vectorize delete my-index

Manage Vectors

# Insert vectors from NDJSON file wrangler vectorize insert my-index --file vectors.ndjson # Query vectors wrangler vectorize query my-index --vector "[0.1, 0.2, ...]" --top-k 10

Config Binding

{ "vectorize": [ { "binding": "SEARCH_INDEX", "index_name": "my-index" } ] }

Hyperdrive (Database Accelerator)

Manage Configs

# Create config wrangler hyperdrive create my-hyperdrive \ --connection-string "postgres://user:pass@host:5432/database" # List configs wrangler hyperdrive list # Get config details wrangler hyperdrive get <HYPERDRIVE_ID> # Update config wrangler hyperdrive update <HYPERDRIVE_ID> --origin-password "new-password" # Delete config wrangler hyperdrive delete <HYPERDRIVE_ID>

Config Binding

{ "compatibility_flags": ["nodejs_compat_v2"], "hyperdrive": [ { "binding": "HYPERDRIVE", "id": "<HYPERDRIVE_ID>" } ] }

Workers AI

List Models

# List available models wrangler ai models # List finetunes wrangler ai finetune list

Config Binding

{ "ai": { "binding": "AI" } }

Note: Workers AI always runs remotely and incurs usage charges even in local dev.

--

5-Dim Analysis
Clarity8/10
Novelty6/10
Utility8/10
Completeness7/10
Maintainability7/10
Pros & Cons

Pros

  • p1
  • p2

Cons

  • c1
  • c2

Related Skills

claude-domain-skills

B
toolAuto-Pilot
72/ 100

“Powerful, but the setup might scare off the impatient.”

my-skills

B
toolAuto-Pilot
72/ 100

“Powerful, but the setup might scare off the impatient.”

terraform-ibm-modules-skills

B
toolAuto-Pilot
72/ 100

“Powerful, but the setup might scare off the impatient.”

Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.

Copyright belongs to the original author cloudflare.