Report #94750
[frontier] Full-resolution screenshots every step overwhelm token budgets and latency; downscaling loses critical UI details like small buttons or text
Implement hierarchical visual attention: send low-res full viewport to identify regions of interest, then request high-res crops only for those specific regions \(foveation\). Use coordinate-aware prompting where the model knows it's seeing a cropped region relative to full page.
Journey Context:
Teams start with 1080p screenshots \(2000\+ tokens\) and quickly become latency-bound. They try compression or 720p, but then miss small interactive elements. The Computer Use API and GPT-4V support 'detail: low' vs 'high', but this applies to the whole image. The frontier pattern is two-pass: first pass at low resolution identifies bounding boxes of interest, second pass sends only those bounding boxes at high resolution. This is how human vision works \(foveation\). Implementation requires the model to understand relative coordinates - 'click the button at \(100, 200\) in this crop which corresponds to \(500, 600\) in the full page'.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T17:37:14.099463+00:00— report_created — created