Cloudflare Introduces Temporary Accounts for Autonomous Worker Deployment

Cloudflare has recently introduced temporary accounts that let AI agents deploy Cloudflare Workers immediately, without first creating or authenticating with a permanent account. If left unclaimed, the accounts and their deployments expire automatically after 60 minutes.

The new feature removes a common automation bottleneck in agent-driven workflows, while preserving a clear handoff to human ownership and limiting the security and operational risks associated with abandoned resources. Using wrangler deploy --temporary, an agent receives a live deployment that remains active for up to 60 minutes, during which a human can claim it and convert it into a permanent account.

Source: Cloudflare blog

While the new feature is designed for AI-generated deployments and background agent sessions, the temporary accounts can also help quickly prototype new ideas on a new Cloudflare account and support first-time Workers evaluations. Sid Chatterjee, principal engineer at Cloudflare, Celso Martinho, VP of engineering at Cloudflare, and Brendan Irvine-Broque, senior director of product at Cloudflare, explain:

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.

AI agents can now deploy websites, APIs, and other agents immediately, without first requiring users to create or authenticate an account. Frictionless temporary accounts let AI agents deploy, test, and iterate without interactive authentication, enabling fully autonomous workflows. Chatterjee, Martinho, and Irvine-Broque add:

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.

The announcement attracted significant attention in the community, with some still questioning whether this really addresses the hard-limit budget. On Hacker News, Simon Willison, co-founder of Lanyrd and co-creator of the Django web framework, comments:

Looks like Cloudflare still haven't shipped the most valuable possible feature for Cloudflare Workers though: hard billing caps.

Ronald Simons, founder of Treenia, comments on LinkedIn:

The internet's identity and authorization models were built assuming a human operator. As agents increasingly create, deploy, acquire, and manage digital assets, temporary credentials solve today's deployment problem, but they also expose a larger question: how will persistent ownership, authority, and accountability be established for agent-driven infrastructure over time?

Source: Cloudflare blog

Among the current limitations, temporary accounts are subject to rate limits and abuse-prevention checks, cannot be used alongside authenticated Cloudflare credentials, and require that claim URLs be handled securely because they grant account ownership.

The new feature requires Wrangler 4.102.0 or later.