Two Browser Use settings speed up flight search by about 10 seconds
Understand this story
Browser Use published an engineering retrospective stating that enabling just two configuration switches reduced the time for its browser agent to find the three cheapest flights on Google Flights from 30.7 seconds to 20.7 seconds, and the example.com task from 10.3 seconds to 6.5 seconds. Specifically: the agent now connects directly first, and switches to a proxy browser when it encounters website blocking; the Ultrafast browser disables the solver by default. Users can try it by setting the model to bu-ultrafast in Browser Use Cloud. The retrospective also mentioned that Priority mode is billed at twice the rate per token, and in replica tests reduced the average per-turn time from 1.20 seconds to 1.02 seconds, saving about 1.9 seconds over a 12-turn task.
AI overview based on source reports · Updated 51 min ago
Coverage timeline
Follow the coverage to explore different perspectives.
- Browser Use BlogTwo Config Flags Cut Our Browser Agent's Flight Search From 30.7 s to 20.7 s
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.
Activity for this story
Not enough continuous observations to show a trend yet.