Cloudflare
The web performance & security company
5.0•184 reviews•4K followers
The web performance & security company
5.0•184 reviews•4K followers
Cloudflare is a leading edge network services provider that offers a wide range of solutions to enhance the security, performance, and reliability of websites and applications. With its global network infrastructure and advanced technologies, Cloudflare empowers businesses to build a faster, more secure, and resilient online presence.
This is the 49th launch from Cloudflare. View more
Cloudflare Temporary Accounts
Launched this week
The moment an agent needs to deploy something, it slams face-first into a wall built for humans. Today we're rolling out Temporary Accounts on Cloudflare Workers. Any agent can now run wrangler deploy — temporary and get a live Worker in seconds.
Free Options
Launch Team
Flowtica Scribe
Hi everyone!
Your agent has 60 minutes to ship its work before you claim it.
@Cloudflare now has temporary accounts for AI agents. With wrangler deploy --temporary, an agent can deploy a real Worker without asking you to sign up, complete OAuth, create an API token, or click through the dashboard.
It gets a temporary preview account, a live workers.dev URL, and a claim link.
The nice part is that the agent can loop during the 60-min window: deploy, test the URL, change the code, redeploy, and verify again.
When the work is useful, you keep it. When it is not, it disappears💨
The 60-minute ephemeral window with iterative redeploy is the right design for agentic workflows. Auth interruptions break agent execution mid-task, and the claim link keeps humans in control of what gets committed. I've hit this exact wall with multi-step automated pipelines. How does state transfer work at claim time? Do KV namespace bindings and Durable Objects carry over, or does the agent need to reconstruct?
DMV by Agent Community
I like the 60-minute temporary window. It feels like a good balance, enough time for the agent to prove the work is useful, but not another abandoned preview environment that lives forever.
Curious how this will work for slightly more complex Worker projects. Can temporary deploys also test bindings like KV, R2, D1, or environment variables, or is the first version focused mostly on simple Workers?
This is smart. The biggest blocker for agents right now is auth and account setup. 60 minutes to deploy and claim is a nice middle ground. What happens to the worker if nobody claims it though? Does it just get wiped?
Disposable identifiers are one of the rare privacy moves that also cut fraud exposure — a throwaway address can't be cross-referenced or resold onto a "sucker list." Curious how you're handling recovery: if someone needs to re-access something tied to a temporary account, what's the flow?
The 60-minute temporary account flow is the part I'd test first for agent workflows, especially when a project needs a few deploy-test-redeploy loops before a human even looks at it. The practical edge case is claim time: if the agent already attached KV, D1, or Durable Objects during the temporary window, does claiming the project preserve those bindings as-is, or does the human need to recreate part of the setup in the real account?
Ephemeral credentials that self-delete in 60 minutes is the sort of attack-surface reduction I wish more products shipped by default. You don't have to leave junk out there racking up billing either. Now someone just has to worry about what the agent deploys to a public URL in that window.