Cloudflare · 2026-06-19 · major
Cloudflare Temporary Accounts — AI agents deploy live Workers in seconds, no signup
Cloudflare's new wrangler deploy --temporary command lets an AI agent provision a live Workers account in seconds without signup. The account stays usable for 60 minutes, after which a human can claim it permanently or let it auto-expire.

Cloudflare's wrangler deploy --temporary spins up a live Workers account for an AI agent in seconds, with no signup or browser OAuth.
Quick facts
| Maker | Cloudflare |
|---|---|
| Command | wrangler deploy --temporary |
| Wrangler version | 4.102.0+ |
| Account lifetime | 60 minutes before auto-expiry |
| Claim flow | Human opens the claim URL, signs up, keeps deployment and resources |
| Auth | auth.md OAuth via WorkOS partnership |
| Supported products | Cloudflare Workers plus resource bindings |
What is it?
Cloudflare Temporary Accounts is a new deployment mode in Wrangler 4.102 that lets an AI agent ship a working Cloudflare Worker without first creating a Cloudflare account. The agent runs wrangler deploy --temporary, gets back an API token, a live Worker URL, and a claim link a human can use to keep the account.
How does it work?
When Wrangler sees --temporary, Cloudflare provisions a fresh preview account on the fly and returns credentials plus a 60-minute claim URL. The agent can iterate, redeploy, and curl the Worker during that window. If nobody claims the account in 60 minutes, Cloudflare deletes it along with every Worker and resource binding it produced. The auth.md protocol from WorkOS describes the discovery flow agents use, and a separate Stripe partnership covers paid-tier provisioning for accounts that get claimed.
Why does it matter?
Most AI agent runs that build software get blocked at the deploy step because the target platform demands a browser-based signup. Temporary accounts unblock the loop: an agent can ship a working Worker, verify the output itself, and hand a live URL to a human who decides later whether to keep it. That removes one of the biggest friction points for autonomous coding agents on Cloudflare's developer platform.
Who is it for?
developers building autonomous coding agents that target Cloudflare Workers
Frequently asked questions
- How long does a Cloudflare temporary account last?
- A Cloudflare temporary account stays active for 60 minutes after wrangler deploy --temporary creates it. During that window the agent can redeploy, run the Worker, and verify the response. If no human claims the account by clicking the returned claim URL, Cloudflare deletes the account and every resource it created.
- How does a human turn a Cloudflare temporary account into a permanent one?
- Wrangler prints a claim URL alongside the deployment output. A human opens that URL inside the 60-minute window, signs up or logs into Cloudflare, and claims the temporary preview account. The deployed Worker and any bindings it created move into the new permanent account without redeploying.
- What Wrangler version do I need for Cloudflare temporary accounts?
- Cloudflare requires Wrangler 4.102.0 or newer for the --temporary flag. The CLI advertises the flag in its help output so agents can discover it the same way they discover other deploy options. Older Wrangler builds will simply not recognise --temporary and fall back to a normal authenticated deploy.
- How does Cloudflare's temporary-accounts feature compare to a regular Workers signup?
- A regular Cloudflare Workers signup requires a browser OAuth flow, email verification, and multi-factor setup before the first deploy. Cloudflare Temporary Accounts skip all three, which is what makes them workable for background AI agents that have no human in the loop at deploy time. Anything the agent ships still has to be claimed by a person to live past 60 minutes.
Try it
wrangler deploy --temporary