Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/openai/skills/llms.txt

Use this file to discover all available pages before exploring further.

The Cloudflare Deploy skill gives Codex the knowledge to deploy across the entire Cloudflare developer platform. Whether you’re shipping a serverless function on Workers, a full-stack app on Pages, or wiring up storage with KV, D1, R2, or Queues, Codex can pick the right product, authenticate with Wrangler, and deploy — all from your workspace. Ask Codex to “deploy this to Cloudflare Workers”, “publish my Pages site”, or “set up a D1 database and deploy” to get started.

Trigger Phrases

Codex activates this skill when it detects Cloudflare deployment intent. Common phrases include:
  • “deploy to Cloudflare Workers”
  • “publish this on Cloudflare Pages”
  • “deploy my Worker and set up KV storage”
  • “ship this to Cloudflare”
  • “set up a D1 database and deploy my app”

Installing

$skill-installer cloudflare-deploy
Restart Codex after installation to pick up the new skill.

Authentication

Codex verifies authentication before any deploy command runs:
npx wrangler whoami

Interactive / Local

One-time browser OAuth flow:
wrangler login

CI / CD

Set an environment variable:
export CLOUDFLARE_API_TOKEN=your_token
Always run npx wrangler whoami before wrangler deploy, wrangler pages deploy, or npm run deploy. If not authenticated, deployments will fail silently or with a generic error.

Choosing the Right Cloudflare Product

Codex uses decision trees from the skill to route you to the right product automatically. The key categories are:

Compute & Runtime

NeedProduct
Serverless functions at the edgeWorkers
Full-stack web app with Git deploysPages
Stateful coordination / real-timeDurable Objects
Long-running multi-step jobsWorkflows
Run containersContainers
Scheduled tasks (cron)Cron Triggers
Lightweight edge logic (modify HTTP)Snippets
Multi-tenant (customers deploy code)Workers for Platforms
Process Worker execution events (logs/observability)Tail Workers
Optimize latency to backend infrastructureSmart Placement

Storage & Data

NeedProduct
Key-value (config, sessions, cache)KV
Relational SQLD1 (SQLite)
Connect existing Postgres / MySQLHyperdrive
Object / file storage (S3-compatible)R2
Message queue (async processing)Queues
Vector embeddings (AI / semantic search)Vectorize
Strongly-consistent per-entity stateDurable Objects storage
Secrets managementSecrets Store
Streaming ETL to R2Pipelines
Persistent cache (long-term retention)Cache Reserve

AI & Machine Learning

NeedProduct
Run inference (LLMs, embeddings, images)Workers AI
Vector database for RAG / searchVectorize
Build stateful AI agentsAgents SDK
Gateway for any AI provider (caching, routing)AI Gateway
AI-powered search widgetAI Search

Networking & Connectivity

NeedProduct
Expose local service to internetTunnel
TCP/UDP proxy (non-HTTP)Spectrum
WebRTC TURN serverTURN
Private network connectivityNetwork Interconnect
Optimize routingArgo Smart Routing
Real-time video / audioRealtimeKit / Realtime SFU

Security

NeedProduct
Web Application FirewallWAF
DDoS protectionDDoS Protection
Bot detection / managementBot Management
API protectionAPI Shield
CAPTCHA alternativeTurnstile

Deployment Workflow

1

Authenticate

npx wrangler whoami
If not authenticated, run wrangler login (local) or set CLOUDFLARE_API_TOKEN (CI/CD).
2

Deploy Workers

For a Cloudflare Worker (serverless function):
npx wrangler deploy
Or if you have a build step:
npm run deploy
Codex loads the detailed Workers reference (references/workers/) for configuration, bindings, and runtime APIs.
3

Deploy Pages

For a full-stack app or static site on Cloudflare Pages:
npx wrangler pages deploy ./dist
Pages connects to your Git repository for automatic deploys on push. Codex loads references/pages/ for routing, build configuration, and Pages Functions.
4

Add Storage Bindings

Codex helps you configure storage bindings in wrangler.toml as needed:
# KV Namespace
[[kv_namespaces]]
binding = "MY_KV"
id = "abc123..."

# D1 Database
[[d1_databases]]
binding = "DB"
database_name = "my-database"
database_id = "def456..."

# R2 Bucket
[[r2_buckets]]
binding = "MY_BUCKET"
bucket_name = "my-bucket"

Platform Coverage

This skill covers the full Cloudflare developer platform. The complete product index Codex can help you deploy to:

Compute & Runtime

Workers, Pages, Pages Functions, Durable Objects, Workflows, Containers, Workers for Platforms, Cron Triggers, Tail Workers, Snippets, Smart Placement

Storage & Data

KV, D1, R2, Queues, Hyperdrive, Durable Objects Storage, Secrets Store, Pipelines, R2 Data Catalog, R2 SQL

AI & ML

Workers AI, Vectorize, Agents SDK, AI Gateway, AI Search

Networking

Tunnel, Spectrum, TURN, Network Interconnect, Argo Smart Routing, Workers VPC

Security

WAF, DDoS Protection, Bot Management, API Shield, Turnstile

Media & Content

Images, Stream, Browser Rendering, Zaraz, Cache Reserve

Real-Time Comms

RealtimeKit, Realtime SFU

Infrastructure as Code

Pulumi, Terraform, REST API

Infrastructure as Code

For teams that prefer IaC, Codex can generate configuration for Pulumi or Terraform, or interact with the Cloudflare REST API directly.
# Pulumi
# references/pulumi/

# Terraform
# references/terraform/

# REST API
# references/api/

Escalated Network Access

If a deploy fails due to network issues (timeouts, DNS errors, connection resets), Codex will ask before retrying with elevated permissions:
The deploy needs escalated network access to deploy to Cloudflare.
I can rerun the command with escalated permissions — want me to proceed?
As with all deploy skills, the authentication check (wrangler whoami) never requires escalated permissions — only the actual deploy command does.

Developer Tools

Codex uses these tools throughout the deployment process:
ToolPurpose
WranglerPrimary CLI for Workers, Pages, and all platform services
MiniflareLocal simulator for Workers (testing without deploying)
C3 (create-cloudflare)Scaffold new Workers and Pages projects
ObservabilityLogs, metrics, and tracing for deployed services
Workers PlaygroundBrowser-based REPL for quick Worker testing

Reference

Build docs developers (and LLMs) love