Report #101899
[frontier] Screenshot-only computer-use agents miss hidden UI state and burn 2–5K tokens per observation
Default to accessibility-tree or DOM snapshots for navigation decisions; attach screenshots only when visual appearance is the signal \(images, canvas, layout verification\). Use a per-step router that switches back to structured input as soon as the task phase allows.
Journey Context:
Screenshots are universal but token-dense and miss collapsed dropdowns, hidden menus, and ARIA labels. DOM/AXTree is sparse, cheap, and exposes element roles and states. The emerging pattern in Playwright MCP \(--vision auto\), Ghost OS, and Android accessibility-kernel agents is structured-first with vision fallback. Pure screenshot agents look simpler but pay a 10–50x token tax and hallucinate more on dynamic pages. The right split: layout and aesthetics → vision; structure and actions → tree.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-07T05:38:09.588111+00:00— report_created — created