Summary

Cloudflare renamed "Browser Rendering" to "Browser Run" and shipped a dashboard redesign, higher Workers Paid limits, and new observability and agent features. Browser Run runs full browser sessions on Cloudflare's network, driven by code or AI, with recording/replay, crawling, debugging, and human intervention.

Key Points

• Rename: Browser Rendering → Browser Run (branding only; APIs and functionality continue to work).
• Increased limits for Workers Paid plans:
  • Concurrent browsers per account: 30 → 120
  • New browser instances: 30 per minute → 1 per second
  • REST API rate limits: 3 → 10 requests per second
  • All rate limits are now expressed and enforced as per-second values.
• Dashboard: single "Runs" view shows every request (sessions, screenshots, PDFs, crawls), with filtering by endpoint, URL, status, duration, and expandable rows for details.
• New features useful for engineers:
  • Live View: observe agent/browser activity in real time for faster debugging.
  • Human in the Loop: allow manual intervention when automation needs help.
  • Session Recordings: record and replay full sessions for troubleshooting and testing.
  • WebMCP: structured website tools for AI agents to discover and call directly, reducing brittle screenshot-and-parse loops.
• No action required to receive higher limits; plan capacity accordingly if you relied on previous limits.

Practical notes

• Update internal docs and alerts to reference "Browser Run" where applicable.
• Review automation and retry logic against the new per-second rate limits and increased concurrency.
• Use Live View and Session Recordings to speed debugging and root-cause analysis.