Report #51675
[research] Agent evals are flaky and unreliable when validating browser-based UI interactions
Shift agent tasks to the CLI verifiable end of the spectrum wherever possible. For browser tasks, use DOM state assertions or accessibility tree comparisons instead of visual screenshot diffing.
Journey Context:
Agents interacting with CLIs return structured exit codes and stdout, making evals deterministic. Browser agents return screenshots or DOMs that change with minor CSS updates, causing high false-positive rates in evals. You cannot scale browser-agent testing without accepting flakiness or shifting assertions to the accessibility tree, which is structurally more stable than raw HTML/CSS.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T17:13:57.666097+00:00— report_created — created