// AI Platform Drift

Browser Run User-Agent now reports Chrome 152 instead of Chrome 119

Cloudflare developer changelog · published 2026-10-31 17:24 UTC
ACTION NEEDED VERIFY_ONLY API
WHAT CHANGEDCloudflare Browser Run updated its default User-Agent string from Chrome 119 to Chrome 152 on 30 October 2026. The /links endpoint now returns absolute URLs instead of relative URLs, and links-only crawls now follow relative links. Browser Run removed distrusted root certificates from its trust store.
WHY IT MATTERSIf you allowlist or pattern-match the Browser Run User-Agent in firewall rules, rate limiters, or analytics, those rules will stop matching requests from Browser Run sessions. Code that expects relative URLs from /links will receive absolute URLs instead.
WHAT TO DOSearch your codebase and infrastructure configs for User-Agent patterns matching Chrome 119 or the old Browser Run string. Update allowlists and matchers to accept Chrome 152. Review any code parsing /links output that assumes relative URLs.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Browser Run - Browser Run now runs Chrome 152
+https://developers.cloudflare.com/changelog/post/2026-10-30-chrome-152/
+Fri, 30 Oct 2026 00:00:00 GMT
+
+Browser Run now runs Chrome 152 by default. Your sessions get current web platform features, rendering fixes, and security patches. You do not need to change your code.
+This release also includes the following improvements:
+
+Updated default User-Agent. The default User-Agent for Quick Actions now reports Chrome 152 instead of Chrome 119. If you allowlist or match the Browser Run User-Agent, update your rules. You can still set your own value with the userAgent parameter. Refer to Automatic request headers.
+Better site compatibility. Quick Actions requests now look more like requests from a regular Chrome browser, so fewer sites block them.
+Large response headers. Pages that return large response headers now load correctly.
+Updated root certificates. Browser Run removed distrusted root certificates from its trust store.
+Absolute links. /links now returns absolute URLs, and links-only crawls now follow relative links.
+Better Markdown output. /markdown and crawl Markdown output now keep code block languages.
+Clearer errors. Quick Actions that time out now return a consistent error. Outbound Workers that throw an exception now return an HTTP error to the browser.
+
+For more information, refer to the Browser Run documentation.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.85, needed 0.5
triage reasoningChrome version upgrade with breaking API changes and User-Agent shifts requiring developer action.
signalsmajor version bump (Chrome 119 → 152) · User-Agent change requiring rule updates · breaking change: /links now returns absolute URLs instead of relative · API behavior change: links-only crawls now follow relative links · certificate trust store modification · Markdown output format change (code block language preservation)
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)