How to Deploy Cloudflare Workers via Temporary Accounts

Cloudflare’s new Temporary Accounts for AI agents feature allows autonomous systems to deploy code to the edge without standard OAuth flows or dashboard interactions. Released as automated agent traffic surpassed 57.5% of total HTML web requests, this mechanism lets agents create ephemeral environments to execute code. You can now configure your AI agents to provision their own infrastructure instantly and hand over the persistent resources to human operators later.

Temporary accounts solve the friction of human-centric authentication in autonomous development loops. Agents can deploy a Worker, run a standard curl command against their own output to verify the implementation, and iterate on the logic until the specific task is complete.

Prerequisites and Installation

To enable temporary deployments, your agent environment must run an updated version of the Cloudflare CLI. Standard API token authentication is bypassed entirely when using this specific deployment path.

Your environment requires Wrangler 4.102.0 or later. Earlier versions will throw a standard authentication error when attempting to deploy without local credentials.

Update Wrangler via npm:

bash npm install -g wrangler@latest

Triggering a Temporary Deployment

The temporary account flow is invoked via a single flag appended to the standard deployment command. Your agent script or language model prompt should be configured to execute this command when the code is ready for verification.

bash wrangler deploy —temporary

Executing this command triggers the creation of an anonymous Cloudflare environment. Wrangler instantly deploys the live Worker and returns the execution URL directly to the terminal output. The agent can parse this standard output to capture the URL for immediate testing.

Account Lifespan and The Claim Process

Temporary deployments remain active for exactly 60 minutes. This window is designed for rapid iteration loops where the agent writes, deploys, and tests code before finalizing the work.

During this 60-minute execution window, Wrangler outputs a “claim URL” alongside the deployment details. The agent must return this claim URL to the human user supervising the workflow.

If the user opens the claim URL and signs in to Cloudflare, the temporary account and all associated resources are permanently migrated into the user’s primary account. If the 60-minute window expires without the claim URL being processed, Cloudflare automatically deletes the temporary account and all deployed edge resources.

Supported Infrastructure

Agents utilizing the temporary deployment flag cannot access the entire Cloudflare ecosystem. The feature supports a specific subset of stateful and stateless primitives necessary for evaluating functional web applications.

Product	Supported in Temporary Mode	Use Case
Workers	Yes	Edge compute execution
Workers Static Assets	Yes	Frontend hosting
Workers KV	Yes	Global key-value storage
D1	Yes	Relational SQL database
Queues	Yes	Asynchronous message processing
Hyperdrive	Yes	Database connection pooling
SSL/TLS	Yes	Automatic certificate provisioning

This architecture ensures that agents building complex workflows involving databases or queues can fully test their implementations before the human operator reviews the claim URL.

Security and Vulnerability Management

Removing the authentication barrier for deployments introduces distinct security considerations. While temporary accounts reduce development friction, they also open avenues for agents to inadvertently deploy insecure code to a live, public-facing URL.

Coinciding with this release, security researchers identified “AutoJack”, a vulnerability pattern where AI agents browsing untrusted websites could be manipulated into executing remote code. If an agent is compromised during its generation phase and subsequently issues a temporary deployment command, it could host malicious endpoints on Cloudflare infrastructure.

Operating agents with deployment privileges requires configuring a robust vulnerability harness. Agents should be isolated in environments that restrict network access beyond the specific endpoints required for their task. Integrating these safety measures directly with the Cloudflare Agents SDK ensures that any code deployed via the --temporary flag has passed automated static analysis before execution.

Monitor your agent’s terminal output parsing carefully. The agent must reliably distinguish between standard deployment logs, runtime errors, and the critical claim URL necessary for preserving successful work.

Configure your automated systems to extract the claim URL using regex and forward it to your primary communication channel immediately upon deployment.