Your agent writes a clean Worker (a small piece of code that runs on Cloudflare's edge, no server to set up) in seconds. Then it hits deploy and stops.

Browser login, MFA, API token copy-paste, 60-second confirmation. A copilot next to you handles that. A background agent with no browser access cannot. It either waits for a click that never comes, or hands you a diff and says "you deploy it."

On 2026-06-19, Cloudflare added one flag to Wrangler:

wrangler deploy --temporary

No account. No OAuth. No MFA. One command, one live public URL, ready to curl and verify.

How it works

Run wrangler deploy with no local credentials. Instead of erroring, Wrangler prints:

To continue without logging in, rerun this command with --temporary.

The agent reads that, reruns with the flag, and Cloudflare handles the rest:

  1. A proof-of-work check. Short delay, no human input.
  2. A temporary account with a random name (Simon Willison got "Educated Celery").
  3. A short-lived token.
  4. The Worker deployed to *.workers.dev.
  5. A live URL plus a claim link. The claim link carries the same power as an API token.

You get 60 minutes. Inside that window the agent can redeploy as often as it wants, reusing the same account. Change code, rerun, recheck.

Open the claim link to sign in and keep the account, including Workers, D1, KV, and bindings. Skip it, everything gets deleted. No orphan accounts.

Supported resources

A temporary deploy gets you:

  • Workers (workers.dev deploys)
  • Static Assets (up to 1000 files, 5 MiB each)
  • KV (read and write)
  • D1 (1 database, up to 100MB)
  • Durable Objects
  • Queues (up to 10)
  • Hyperdrive (up to 2 configs, 10 connections)
  • SSL/TLS certificate issuance

Workers, static files, a database, and a queue, all without signing up. Production still belongs on a permanent account. But the cost of "let me just try this" dropped to zero.

Why this matters: custody

The feature is a CLI flag. The shift underneath it is bigger.

--temporary turns the first run into a lease: deploy now, verify on a real URL, iterate for an hour, claim it or let it vanish. Short lifetime, bounded caps, explicit claim path, automatic cleanup. If you're building agent-first infrastructure, this is the shape to study.

Agent platforms will get compared on how cleanly they hand running software back to you, your team, or your client. Code quality is table stakes. Custody is the differentiator.

The bigger picture

Cloudflare didn't ship this alone. In late April, they partnered with Stripe on a production path: agents can create a permanent account, attach billing, buy a domain, and get an API token, all programmatically.

Put both together:

  • Temporary (try it): no account, 60 minutes, free, auto-deleted.
  • Stripe Projects (run it): account, billing, domain, long-running.

Zero-cost sandbox to paid production, one pipeline. Onboarding rebuilt for agents: command line, short lifetimes, automatic cleanup.

Watch out for

The HN thread flagged a few concerns:

  • Abuse. Phishing pages, throwaway bot farms. Sixty minutes limits exposure, but it is enough time to run. Cloudflare uses proof-of-work and rate limits. Whether that holds, we'll see.
  • Legal gray area. An agent accepting the ToS for you is untested ground. Leak the claim URL and you leak ownership.
  • 60 minutes is tight. Fine for a hello world, short for a complex prototype. No extension or pause yet.
  • type yes confirm. Still trips pure automation.

Community consensus: drop the barrier to zero first, add guardrails after. That order tends to work.

Simon Willison tested it

On 2026-06-21, Simon Willison had GPT-5.5 in Codex Desktop build an HTTP redirect resolver and deployed it with npx wrangler deploy --temporary. His take: "The temporary deployment worked as advertised." Account name: "Educated Celery." Live URL: cloudflare-redirect-resolver.educated-celery.workers.dev. Claim page: red countdown, resource list, Claim Account button.

One point he made: this isn't only for agents. A free, disposable live environment works for PR previews, code reviews, and pairing on a bug. One command, one working link, nothing to clean up.

Historical context

Heroku had review apps. Netlify had deploy previews. Vercel put preview URLs in the Git flow. All of them require an account first. Cloudflare pushed preview down to the CLI, to where you need no account at all. For a human, that's convenient. For an agent that can't click through email verification and OAuth, it's closer to a requirement.

Try it

Four steps, ten minutes:

  1. Update to the latest Wrangler.
  2. Point your agent at a small Worker and let it run wrangler deploy --temporary.
  3. Curl the live URL. Check the output against the code.
  4. Claim it or walk away.

The takeaway

Temporary accounts don't solve everything. Production billing, long-term identity, cross-platform orchestration are still open problems. They solve one thing nobody else had: an agent going from code to live URL in a single command, zero human input. Free 60-minute window, auto-created account, auto-cleaned, yours if you claim it.

Once this pattern proves out, GitHub, Vercel, Netlify, AWS, and GCP will face the same question: when the thing calling your API can't log in through a browser, is your product still usable? Cloudflare answered first.

Sources