Summary
Cloudflare renamed Browser Rendering to Browser Run on April 15 and used the relaunch to raise Workers Paid concurrency and session-creation limits. The product is now framed explicitly as an AI and automation primitive for running full browser sessions on Cloudflare's network.
What changed
Cloudflare rebranded Browser Rendering as Browser Run and increased paid-plan browser concurrency, session creation, and REST API rate limits.
Why it matters
The rename is more than cosmetic. Cloudflare is clarifying that this is an agent-runtime product, not just a rendering utility, and backing that up with materially higher limits for production automation workloads.
Evidence excerpt
Cloudflare says Browser Run lets users run full browser sessions for code or AI and increased paid-plan concurrent browsers from 30 to 120 while raising creation and API limits.