Browser Use Blog· Magnus Müller·· 21 hr agoAI score34
Two Config Flags Cut Our Browser Agent's Flight Search From 30.7 s to 20.7 s
Two Config Flags Cut Our Browser Agent's Flight Search From 30.7 s to 20.7 s
AI summary
Browser Use reports that switching to OpenAI's priority tier and starting direct instead of through a residential proxy took its Google Flights task from 30.7 s to 20.7 s on staging, with the same harness still 5.3 s slower through a US proxy on Oct 9 (25.3 vs 20.0 s, n=8). Other causes included a settle detector that never fired because Google Flights rewrites a CSS class every frame, an always-on captcha detector burning 32-35% main-thread CPU while idle, and a longer prompt; the post notes about 3.4 s of prod's 18 s model time remains unexplained.
Source: Browser Use Blog · browser-use.com