cf-temp-deploy

name	cf-temp-deploy
description	Deploy a Cloudflare Worker to a public URL with no signup or login using `wrangler deploy --temporary`. The temporary account auto-expires in 60 minutes unless claimed. Use when the user wants to quickly ship/demo a Worker, deploy without Cloudflare credentials, or asks about Cloudflare temporary accounts.

cf-temp-deploy

Ship a Cloudflare Worker to the public internet with zero authentication.

When to use

• User wants a throwaway/demo deploy of a Worker without logging into Cloudflare.
• An agent needs to deploy without provisioned credentials.
• User mentions "temporary account", --temporary, or quick Worker demo.

Steps

1. Ensure a Worker exists. Minimal scaffold:

   cat > worker.js <<'EOF'
   export default { fetch() { return new Response("ok\n"); } };
   EOF
   cat > wrangler.toml <<'EOF'
   name = "my-worker"
   main = "worker.js"
   compatibility_date = "2025-06-01"
   EOF
   

   • name must be lowercase/hyphen.
   • compatibility_date MUST be today or earlier — a future date fails with code 10021.

2. Deploy:

   bunx wrangler deploy --temporary   # npx works too
   

   First run solves a proof-of-work challenge and provisions the temp account.

3. Report back to the user:

   • the live https://<name>.<account-slug>.workers.dev URL,
   • the Claim URL (60-min window to make the account permanent),
   • that the account + all bound resources are wiped after 60 minutes unless claimed.

4. Verify it's live:

   curl https://<name>.<account-slug>.workers.dev
   

Notes

• --temporary is not listed in wrangler deploy --help (as of 4.103.0) but works.
• Re-deploying in the same directory within the window reuses the account (reused).
• Treat the Claim URL as a credential — don't paste it into shared/public output unredacted.
• For anything that must persist, tell the user to claim the account or use wrangler login.