On June 19, 2026, Cloudflare shipped Temporary Accounts for Agents: an AI coding agent runs “wrangler deploy –temporary” and pushes a website, an API, or another agent to Cloudflare Workers without ever creating an account, pasting an API token, or opening a dashboard. The deployment lives for 60 minutes, during which the agent can edit code, redeploy, and curl the output to verify its own work. A human can claim the whole thing — account, bindings, databases — through a URL; if nobody does, Cloudflare deletes the account and everything in it.
The target is the last human-shaped obstacle in agent deployment. Browser-based OAuth flows, MFA prompts, and copy-pasted tokens are merely annoying for an interactive copilot. For a background agent with no human in the loop, they are a hard stop.
The Last Wall Agents Hit: Accounts
Cloudflare’s post lays out three arguments. First, background AI sessions have no human in the loop “and are becoming the norm.” Second, “trial-and-error is the agent’s superpower” — agents need a tight write, deploy, verify loop, not a one-shot upload. Third, agent platforms expect deployment to just work, without credentials or extra steps. The authors — Sid Chatterjee, Celso Martinho, and Brendan Irvine-Broque — state the goal plainly: “Let your agent code and ship.”
How the 60-Minute Temporary Account Works
There are two paths. The CLI path serves agents and agentic tools: Wrangler 4.102.0 and later accepts “wrangler deploy –temporary” in an unauthenticated, non-interactive session. Wrangler handles the proof-of-work challenge, receives a temporary account and API token, caches the credentials until they expire, and allows repeated redeployments inside the window.
The REST path serves platforms that want control: request a proof-of-work challenge at the provisioning endpoint, solve it as a sequential SHA-256 checkpoint chain, and post the solution with an explicit terms-of-service acceptance. The backend receives the account’s API token and the claim URL, deploys the supported resources, and returns only the preview and claim URLs to the end user — the token never reaches the browser.
One small detail does a lot of work: when authentication fails, Wrangler now prints a message telling the agent about the –temporary flag. Agents discover the feature on their own; nobody has to teach them.
Claiming, Limits, and the Security Model
A claim must be fully completed within 60 minutes — opening the URL is not enough. Claimable resources are broader than the name suggests: Workers deployments on workers.dev, up to 1,000 static assets at 5 MiB each, full Workers KV namespaces, one D1 database with 100 MB of storage, Durable Objects bindings and migrations, two Hyperdrive configurations, up to 10 Queues, and mTLS certificates. The limits are equally explicit: –temporary works only in an unauthenticated state, account creation is rate-limited, and the FedRAMP High endpoint is not supported.
The security model is simple and worth internalizing: the claim URL is a bearer credential. Anyone holding it can take ownership of the account. Cloudflare’s docs instruct platforms to keep the token and URL in backend storage and delete both by expiration time. Claiming does not grant the platform permanent access, either — later deployments still require a normal login or OAuth flow.
What It Means for the Agent Platform Stack
Cloudflare frames this as “one more step toward frictionless agentic deployments,” and points at two earlier tiles in the same mosaic: a Stripe partnership co-designing a protocol that lets agents provision Cloudflare accounts, subscriptions, domains, and API tokens on a user’s behalf, and WorkOS’s auth.md, an open standard from the prior month for provisioning accounts through existing OAuth flows.
For developers, the signal is that deployment infrastructure is removing “a human signs up” from the critical path. Fully unattended workflows — scheduled background agents like Cursor Automations — move one step closer to end-to-end autonomy. The Hacker News thread (249 points, 151 comments) split between enthusiasm and the two questions that will decide adoption: how abuse prevention holds up when account creation gets this cheap, and who owns cleanup for unclaimed resources. Those answers determine whether temporary accounts stay an experiment or become the default path for agent deployments.
Sources
- Temporary Cloudflare accounts for agents — Cloudflare Blog
- Claiming temporary deployments — Cloudflare Docs
- Temporary Cloudflare accounts for AI agents — Hacker News
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.