cloudflare-temporary-deploy

Deploy Cloudflare Workers to live workers.dev URLs without an account using wrangler --temporary.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/loteiron/ZeusAgent --skill cloudflare-temporary-deploy-loteiron
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cloudflare-temporary-deploy
Source: https://github.com/loteiron/ZeusAgent/tree/main/optional-skills/web-development/cloudflare-temporary-deploy
Command: npx skills add https://github.com/loteiron/ZeusAgent --skill cloudflare-temporary-deploy-loteiron

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Deploying a Cloudflare Worker normally requires creating an account, logging in via OAuth, or managing API tokens, which blocks agents and autonomous sessions that just need a quick live URL. This Skill deploys a Worker to a live workers.dev URL with zero account setup using wrangler's --temporary flag. ## Core Features & Use Cases - Account-free deployment: Run npx wrangler@latest deploy --temporary to get a live workers.dev URL and a claim URL valid for 60 minutes. - Structured output parsing: Pipe deploy output through scripts/parse_deploy_output.py to extract the live URL, claim URL, account state, and expiry as JSON. - Self-verifying deploy loop: Deploy, curl the live URL to confirm the response matches the code, then redeploy and iterate within the reused temporary account. - Use Case: In a background coding session, scaffold a minimal Worker, deploy it with --temporary, verify it with curl, and hand the user a claim URL so they can keep the deployment before it auto-deletes. ## Quick Start Ask the agent to deploy the current Worker project to a temporary Cloudflare URL and verify it is live with curl.

Frequently Asked Questions about cloudflare-temporary-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a Cloudflare Worker without an account?▼

Run npx wrangler@latest deploy --temporary from the project directory. Cloudflare provisions a throwaway account, deploys the Worker, and prints a live workers.dev URL plus a claim URL valid for 60 minutes.

How to parse wrangler deploy output for the live URL?▼

Pipe the deploy output into the included parser: npx wrangler@latest deploy --temporary 2>&1 | python scripts/parse_deploy_output.py. It prints JSON with live_url, claim_url, account, account_state, expires_minutes, and deployed fields.

What Wrangler version supports the --temporary flag?▼

Wrangler 4.102.0 or later introduced --temporary. The flag is hidden from --help, so verify with npx wrangler@latest --version and always invoke a pinned recent version rather than a stale global install.

Why does wrangler --temporary fail with an auth error?▼

The --temporary flag errors by design when any Cloudflare credential is present, including a prior wrangler login or CLOUDFLARE_API_TOKEN and CLOUDFLARE_API_KEY environment variables. Unset the variables or run wrangler logout first.

How long does a temporary Cloudflare deployment last?▼

Temporary deployments auto-delete after 60 minutes unless the user opens the claim URL to take ownership of the account. The window is not extendable, so production or long-lived hosting requires a permanent account.

When should I not use wrangler --temporary?▼

Avoid it for production deploys, CI/CD pipelines, and any hosting that must outlive one hour. Use wrangler login or a CLOUDFLARE_API_TOKEN with a permanent account for those scenarios.