01
Background AI sessions have no human in the loop
And they're becoming the norm. Any auth step that needs a browser, a copy-paste, or "click here in 60 seconds" means an agent gets stuck — and may choose to deploy elsewhere.
Agents can now run wrangler deploy --temporary and deploy a Worker to Cloudflare
— no sign-up, no API token, no copy-paste. The temporary deployment stays live for 60 minutes;
claim it to make it permanent, or let it expire on its own.
$ npx wrangler deploy --temporary
Total Upload: 1.24 KiB / gzip: 0.63 KiB
Worker Startup Time: 18 ms
Worker Sandbox: containers
Your Worker has access to the following bindings:
env.ASSETS (Assets)
Uploaded temp-tan-adverb-7b3 (5.20 sec)
Deployed temp-tan-adverb-7b3 triggers (0.71 sec)
https://temp-tan-adverb-7b3.workers.dev
Temporary Account URL: https://temp.cloudflare.com/abc123
Current Version ID: 7f1a8b9c-3d2e-4a11-b5e6-9a8c0d1e2f30
Temporary account expires in 60 minutes. To make it permanent, claim it.The problem
Everyone's writing code with AI agents today. But the moment an agent needs to deploy something — and needs to sign up and create an account — it slams face-first into a wall built for humans: a browser-based OAuth flow, a dashboard to click through, an API token to copy-paste, a multi-factor authentication prompt to satisfy.
For an interactive copilot sitting next to a developer, that's annoying. For a background agent, it's a hard stop.
The fix
Any agent can now run wrangler deploy --temporary and deploy a Worker to Cloudflare.
This temporary deployment stays live for 60 minutes, during which time you can
claim the temporary account, making it permanently your own. If you don't, it expires on its own.
Our goal? Let your agent code and ship.
Why frictionless deployments matter
And they're becoming the norm. Any auth step that needs a browser, a copy-paste, or "click here in 60 seconds" means an agent gets stuck — and may choose to deploy elsewhere.
Agents need a tight write → deploy → verify loop. They need cheap, throwaway deployment targets so they can curl their own output and decide whether they got it right.
Agent platforms are building their own ways for code to "just work" without extra steps or credentials. People are starting to expect that this process just works, without needing to sign up for other services they've never used or heard of.
How it works
Temporary accounts are built around Wrangler, our Developer Platform command-line interface (CLI) tool that lets developers bootstrap new projects, manage their configurations and resources, and deploy and update them.
Wrangler usage is widely documented online and agents know how to use it very well. But if you
hadn't yet signed in and granted Wrangler permission to your Cloudflare account, the agent would
get stuck at the sign-up and authentication step. So how do agents and LLMs know that this new
--temporary flag in Wrangler exists — and actually use it without a human telling them to?
We updated Wrangler to prompt the agent with a message that tells it about the
--temporary flag.
▲ It looks like you are not signed in. Running wrangler as an agent?
Try: wrangler deploy --temporary
It will give you a temporary Cloudflare account, deploy your Worker,
and provide a URL your user can claim within 60 minutes.
$ wrangler deploy --temporary
Cloudflare provisions a temporary account, gives Wrangler an API token,
and provides a claim URL the agent hands back to the human.Let's go over every step of the flow
Fire up your favorite coding agent and write a prompt to deploy a "hello world" app in build mode:
Make a very simple hello world Cloudflare Worker in TypeScript and deploy it using wrangler, don't ask me questions, do the best you can
The agent will run Wrangler, pick up the --temporary flag from the output
messages, build your script, and deploy it instantly — no human in the loop required.
› wrangler deploy --temporary
› curl https://temp-tan-adverb-7b3.workers.dev
Hello World! ✓ verified against src/index.ts
The agent wrote the script, deployed it with --temporary, curled the preview link,
and verified the result matches the code.
Agentic coding is often not about a single deployment. A session can go through a cycle of multiple code changes. Not a problem: the agent can iterate on the Worker script and redeploy the changes as many times as it wants — within the 60-minute claim window.
Now change hello world to "hello cloudflare" and redeployWatch the agent change the source code, reuse the previously created temporary account, redeploy a new version, and recheck the result.
› wrangler deploy --temporary # reuses temp-tan-adverb-7b3
› curl https://temp-tan-adverb-7b3.workers.dev
hello cloudflare ✓Claiming the account
At any point, you can claim the temporary account and make it yours permanently. When you click the claim link you will be taken to a page where you can either sign up for or sign in to Cloudflare, and then claim the temporary account that your Worker was deployed to. This includes claiming not just Workers, but resources like databases and other bindings, too.
The road to frictionless agentic deployments
This is just one way we're eliminating the signup barrier for agents.
A new protocol we co-designed that lets agents provision Cloudflare on behalf of their users — creating an account, starting a subscription, registering a domain, and getting an API token to deploy code, with no copy-pasting tokens or entering credit card details.
Last month, we collaborated with WorkOS on the launch of auth.md, which
anyone can adopt, to let agents provision new accounts using well-established, existing
OAuth standards.
Frictionless, throwaway, self-expiring Cloudflare accounts that any agent can spin up with a single flag. One more step — and there's a lot more coming.
Update Wrangler, fire up your favorite coding agent, and let it ship a Worker in the time it takes you to read this paragraph.
Share what you've built on X or hop into the Cloudflare Community.