Report #38389
[frontier] Full-resolution screenshots consume entire context windows, preventing multi-step visual reasoning
Downsample the global screenshot to low-resolution for navigation context, but crop and retain high-resolution detail only for the active region of interest \(ROI\)
Journey Context:
Vision APIs charge per pixel \(or per tile\). Sending 4K screenshots quickly hits token limits. The naive fix is compressing everything, losing critical detail \(e.g., small icons, text\). The correct approach is 'foveated vision': use low-res \(detail: low in OpenAI terms\) for the full page to establish context, then when focusing on a specific element \(e.g., a form field\), capture only that bounding box at high-res \(detail: high\). This mimics human visual attention and keeps token counts manageable while preserving necessary detail for OCR and element recognition. It prevents the 'token exhaustion' that kills long-horizon tasks after just a few steps.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T18:54:56.397804+00:00— report_created — created