By Every AI coding agent hits the same wall eventually. The code works, the tests pass, and then the agent tries to deploy — and finds itself staring at a browser-based OAuth flow it cannot complete, a dashboard it cannot click through, an MFA prompt it cannot satisfy. For headless agents, that’s not a speed bump. It’s a hard stop. On June 19, Cloudflare took a sledgehammer to it.
What Temporary Accounts Actually Are
wrangler deploy --temporary lets any unauthenticated Wrangler client deploy a live Cloudflare Worker with no credentials and no signup. Run the command, and three things happen automatically: Cloudflare provisions a temporary preview account, issues Wrangler an API token to work with, and generates a claim URL. The Worker goes live on a workers.dev subdomain in seconds. The agent hands the claim URL to a human — or logs it somewhere — and moves on.
The feature requires Wrangler 4.102.0 or later. If Wrangler is already authenticated, --temporary returns an error by design: use wrangler login for that. This is explicitly not a production deploy flow — it is for the moment before a human is in the loop.
What the 60-Minute Window Means
The temporary account lives for 60 minutes. Within that window, a human opens the claim URL in a browser, signs in or creates a Cloudflare account, and takes permanent ownership. Everything transfers: the Worker code, KV namespaces, D1 databases, Durable Objects, Queues — not just the deployed binary. If nobody claims it, the account and every resource attached to it deletes automatically.
This is a clean trust model. The agent does the work; the human claims the output. It is not anonymous hosting, and it is not a backdoor into Cloudflare’s infrastructure. It is a structured handoff with a hard deadline.
Supported products in the temporary account include Workers, Workers Static Assets, Workers KV, D1, Durable Objects, Hyperdrive, Queues, and SSL/TLS certificates — enough to deploy a meaningful application, not just a hello-world endpoint. Full documentation on claim deployments is in the Cloudflare Workers docs.
Why This Matters Beyond the Feature Itself
Agents writing code and opening pull requests is table stakes in 2026. Tools like Cursor, Codex Remote, and Claude Code already do that well. The gap that remained was the deploy step — the moment where autonomous work turned back into a human task because the cloud needed a human to create an account.
Temporary Accounts closes that gap. The build → test → deploy loop can now run completely autonomously for a first-pass deploy. AI pair programmers can ship working demos mid-session without breaking the user’s flow. CI agents can provision live preview environments without pre-configured credentials. Devtools built on LLMs can give users a running URL, not just a code diff.
The practical unlock is significant: if you are building developer tooling with an agentic backend, you no longer need to require users to create a Cloudflare account before they see their agent’s output running live.
The Larger Pattern: Cloudflare Is Building the Agentic Cloud
Temporary Accounts did not ship in isolation. It is part of a systematic effort to rearchitect cloud infrastructure for the agent era. Two related moves are worth tracking.
First, auth.md — an open protocol Cloudflare co-developed with WorkOS. Host a file at /.well-known/auth.md on your domain and you tell agents exactly how to register users on your platform: which OAuth flows you support, which scopes you expose, how credentials get issued. Cloudflare, Firecrawl, Resend, and Monday.com have already shipped it.
Second, the Cloudflare and Stripe Projects integration lets agents create Cloudflare accounts, buy domains, start subscriptions, and get API tokens — all without a human touching a browser. Temporary Accounts handles the pre-account phase. Stripe Projects handles the post-account billing handoff. Together, they cover the full signup-to-deploy lifecycle for agents building on Cloudflare.
For the bigger picture on what Cloudflare shipped across Agents Week 2026, the recap post covers all 30-plus releases.
What to Do Now
If you are building anything with AI agents, this is worth an hour of your time this week. Update Wrangler first:
npm install -g wrangler@latestThen try the flow. Make sure you are logged out locally (wrangler logout), then run wrangler deploy --temporary in a project. You will get a live URL and a claim link. Open the claim link and walk through the account creation flow — that is exactly what your users will experience when your agent ships their first deployment.
If you are building devtools or a coding agent: integrate the claim URL into your UX. Return it alongside the Worker URL with a clear “click here to keep this deployment” prompt. That is the handoff Cloudflare designed this around.
For production and CI/CD, nothing changes — use wrangler login or a scoped API token. Temporary Accounts is for the moment before permanence, not a replacement for proper credential management. Use it for what it is: the fastest path from agent output to running infrastructure a human can claim.
