Right now, everyone is building software with AI agents. But the second an agent has to deploy something — and needs to register, create an account, or log in — it runs straight into a barrier designed for people: a browser-based OAuth flow, a dashboard full of buttons to click, an API token to copy and paste, a multi-factor authentication prompt to complete. For an interactive coding assistant sitting beside a developer, that’s a nuisance. For a background agent running autonomously, it’s a complete roadblock.
Today we’re introducing Temporary Cloudflare Accounts for Agents.
Agents can now deploy websites, APIs, and agents immediately, without needing to create an account first.
Any agent can now run wrangler deploy --temporary and deploy a Worker to Cloudflare. This temporary deployment remains active for 60 minutes, during which you can claim the temporary account and make it yours permanently. If you don’t claim it, it simply expires.
Our goal? Let your agent write code and ship it.
Why seamless deployments matter for AI agents
Frictionless temporary accounts are more important than they might initially appear:
Background AI sessions operate without any human involvement, and this is becoming standard. Any authentication step that requires a browser, a copy-paste action, or “click here within 60 seconds” means the agent gets stuck and may decide to deploy somewhere else entirely.
Trial and error is the agent’s greatest strength. Agents rely on a rapid write → deploy → verify cycle. They need inexpensive, disposable deployment targets so they can test their own output and determine whether it’s correct.
Agent platforms are creating their own methods for deploying code that “just works” without extra steps or credentials. Users are beginning to expect this process to work seamlessly, without having to sign up for unfamiliar services they’ve never used or even heard of.
Temporary accounts are built on top of Wrangler, our Developer Platform command-line interface (CLI) tool that lets developers scaffold new projects, manage their configurations and resources, and deploy and update them.
Wrangler usage is extensively documented online and agents are very familiar with how to use it. But if you hadn’t yet signed in and granted Wrangler permission to your Cloudflare account, when the agent tried to deploy, it would get stuck at the sign-up and authentication step. And you might reasonably ask: How do agents and LLMs know that this new --temporary flag in Wrangler exists, so that they actually use it without a human explicitly telling them to?
To address this, we updated Wrangler to prompt the agent with a message that informs it about the --temporary flag:
When the agent discovers this, and then runs wrangler deploy again with the --temporary flag, Cloudflare provisions a temporary account for the agent to use, gives Wrangler an API token to work with, and provides a claim URL that the agent can pass back to the human.
Let’s walk through every step of the flow
Deploying and iterating on a new project
Make sure you’re running the latest Wrangler release, launch your preferred 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 intervention needed:
As you can see, the agent wrote the script, deployed it using the --temporary flag, curled the preview link it received from the output, and verified that the result matches the code.
This is great, but agentic coding is rarely about a single deployment. A session can go through a cycle of multiple code changes. This isn’t 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). Type this prompt:
Now change hello world to "hello cloudflare" and redeploy
Watch the agent modify the source code, reuse the previously created temporary account, redeploy a new version, and recheck the result:
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
Either log in to or create a Cloudflare account, then claim the temporary account your Worker was deployed to. This applies not only to Workers but also to resources such as databases and other bindings.
If you fail to claim these temporary accounts within 60 minutes, they will be removed automatically.
Paving the way for seamless agent-driven deployments
This is just one of the approaches we’re using to remove the signup hurdle for agents. We recently revealed a collaboration with Stripe along with a new jointly developed protocol that enables agents to set up Cloudflare on behalf of their users — handling account creation, subscription initiation, domain registration, and obtaining an API token for code deployment, all without requiring users to copy-paste tokens or manually enter payment information. Last month, we teamed up on the release of auth.md, an open standard anyone can implement, allowing agents to create new accounts through widely recognized OAuth protocols.
There’s a great deal of activity in this area, and we’re thrilled to continue simplifying the process for agents to leverage Cloudflare and for developers to prepare their applications for agent compatibility. Temporary accounts represent another milestone on the path to effortless agent-driven deployments — more updates are on the way.
Temporary accounts come with certain restrictions, and their functionality may evolve over time; consult the developer documentation for the latest details, then start building. Direct your agent toward Cloudflare, observe how far it progresses, and let us know what could be improved or what impressed you — share your creations on X or join the Cloudflare Community.
