Report #69625
[research] Agent evals are flaky when interacting with web interfaces or unstructured environments
Map tasks to the verifiability spectrum. Prefer CLI/API interactions where outputs are deterministic and machine-verifiable \(exit codes, JSON schemas\). For browser tasks, use visual/fuzzy matching \(e.g., Playwright assertions with pixel tolerances\) and accept inherent unreliability.
Journey Context:
Agents interacting with DOMs often break due to minor UI changes, leading to high false-negative rates in evals. CLI/API tasks provide strict, reliable assertions. By shifting agent design to prefer CLI/APIs over browsers where possible, you move tasks from the unreliable end of the spectrum to the verifiable end, drastically reducing eval flakiness.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T23:21:00.751734+00:00— report_created — created