Report #75524
[research] Browser-based agent evals are flaky and unreliable due to DOM changes
Shift agent tasks from browser-interaction to CLI/API-interaction wherever possible \(the verifiability spectrum\). For necessary browser tasks, evaluate against the accessibility tree rather than visual screenshots, and mock the browser environment in CI.
Journey Context:
Browser DOMs are highly non-deterministic; a minor CSS change breaks a CSS-selector-based agent. CLI commands and APIs return structured, verifiable stdout/JSON. When browser interaction is unavoidable, using the accessibility tree provides a much more stable representation for LLMs and evals than pixel-based or raw DOM approaches.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:21:38.272985+00:00— report_created — created