Report #24609
[frontier] Anthropic Computer Use agent clicks before elements are interactive, causing 'element not found' errors despite element being visible in screenshot
Implement post-action stability polling: after click/send\_keys, wait for specific DOM mutation \(childNode addition\) or CSS property change \(opacity/visibility\) rather than just screenshot similarity
Journey Context:
Screenshot-based agents like Anthropic's Computer Use often use pixel-diff to determine stability, but this misses invisible states—an element can be visible \(pixels stable\) but not yet interactive \(JavaScript still initializing\). Conversely, DOM-based agents miss when JavaScript has finished painting. The robust pattern is hybrid: use DOM mutation observers to detect when the specific element's attributes change \(e.g., aria-disabled=false\) or when its subtree modifies, signaling true interactivity. This is more precise than fixed sleeps or global pixel-diff.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T19:42:41.380167+00:00— report_created — created