Cloudflare lets AI agents deploy first, sign up later with temporary accounts

Cloudflare has launched temporary accounts that let AI coding agents deploy code without first navigating the human-oriented signup gauntlet of OAuth flows, dashboards, copy-pasted API tokens, and MFA prompts. Running wrangler deploy --temporary provisions a throwaway account on the fly, hands Wrangler a working API token, and pushes a live Worker that survives for 60 minutes. A human can claim that account via a returned URL to keep it permanently—along with any databases and other bindings created—or let it expire automatically.

The feature is aimed squarely at background agents that operate with no human in the loop, where any interactive auth step is a hard stop rather than a minor annoyance. It also supports the fast write-deploy-verify loop agents rely on, giving them cheap, disposable targets to curl their own output and check their work, then redeploy repeatedly within the claim window. To make agents aware of the flag without being told, Cloudflare modified Wrangler so that a blocked deploy prints a message advertising --temporary, which agents pick up and act on autonomously.

The move is part of a broader land grab over agent onboarding: Cloudflare cites a Stripe partnership and co-designed protocol for agents to provision accounts and subscriptions on a user’s behalf, plus collaboration with WorkOS on auth.md for OAuth-based agent signups. The strategic logic is competitive—if signing up is friction, an agent will simply deploy somewhere else, so removing the barrier is about capturing agent-driven workloads before rivals do. The temporary accounts carry unspecified limitations that may shift over time.