cloudflare-temporary-deploy

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

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

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 autonomous or background agent sessions. This Skill deploys a Worker to a live workers.dev URL with zero account setup using wrangler's hidden --temporary flag, giving a tight write, deploy, and verify loop. ## Core Features & Use Cases - Accountless Deployment: Uses wrangler deploy --temporary to provision a throwaway Cloudflare account and publish a Worker to a live URL in one command. - Structured Output Parsing: Ships a stdlib-only Python script that extracts the live URL, claim URL, account state, and expiry window from wrangler output as JSON. - Self-Verifying Deploy Loop: Guides curl-based verification of the live URL and safe redeploys within the 60-minute claim window. - Use Case: In an autonomous coding session, scaffold a minimal Worker, deploy it with npx wrangler@latest deploy --temporary, curl the live URL to confirm the response body, and hand the user the claim URL to keep the deployment. ## Quick Start Ask the agent to deploy your Worker project to a temporary Cloudflare URL and verify it is live, then share the claim link before it expires.

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 a project containing a wrangler.toml or wrangler.jsonc and an entry script. 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 Python script: `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 using only the standard library.

What Wrangler version supports the --temporary flag?▼

Wrangler 4.102.0 or later introduced the --temporary flag. The flag is hidden from `wrangler deploy --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`, CLOUDFLARE_API_TOKEN, CLOUDFLARE_API_KEY, or cached OAuth in ~/.wrangler. Unset the environment variables or run `wrangler logout` before retrying.

How long does a temporary Cloudflare deployment last?▼

Temporary deployments expire after 60 minutes and are not extendable. The user must open the claim URL within that window to keep the deployment and its resources; otherwise the account and everything in it auto-deletes.

When should I not use wrangler --temporary for deployment?▼

Avoid it for production or CI/CD, where a permanent account with `wrangler login` or CLOUDFLARE_API_TOKEN is appropriate. It is also unsuitable for long-lived hosting beyond 60 minutes and fails when Wrangler is already authenticated.