ResearchResearch paper

Malva traces silent GUI-agent failures into the tool layer: 335 real defects expose broken state and feedback contracts

An empirical study submitted October 21 confirms 335 tool-mediated interaction defects from roughly 2,000 issues across 40 open-source GUI-agent applications. It groups them into 11 state-representation, transition and synchronization patterns. Ninety percent of the applications contain multiple defect types; 86.6% of defects produce incorrectness, including 119 wrong behaviors without a fail-stop signal.

Why it matters

A generative interface or computer-use agent can reason correctly yet diverge from the live UI because a screenshot is stale, focus is wrong, an action precondition is missing, or success is reported too early. The study treats observation, action and feedback tools as deployed product code, moving acceptance from whether a model can click toward whether the tool contract can preserve and verify state.

A closer look

The authors manually confirm issue, commit and execution evidence to build the Malva defect library, organized across observation, reasoning and planning, execution, and environment feedback. Patterns include target-grounding error, progress-check failure, context-budget overflow, tool-schema mismatch, parameter-semantics error, missing execution preconditions and temporal feedback mismatch. MalvaGuard supports Python, JavaScript and TypeScript. On a separate 20-application corpus with 112 real defects, it reports 150 defects, 86 of them true positives, for 57.3% precision and 76.8% recall. The paper releases the application list, defect library, checker source, detailed results and usage guide.

Who this is for

Engineering and test teams building GUI agents, browser, desktop or mobile automation, generative-UI action tools, acceptance platforms and runtime safety boundaries

Original sources

Revisions & corrections (1)

— Backfill a primary-source empirical study with a public artifact that directly informs GUI-agent and generative-interface tool reliability. It adds failure taxonomy, quantified evidence, a checker, and explicit limitations not already represented in the catalog.

Related events

Research

A second, independent VeriCUA turns GUI-task acceptance into active evidence gathering with abstention

A Google and University of Hong Kong team submitted a separate project also named VeriCUA on October 29. It inspects an environment or recording before constructing a task rubric, then gathers missing evidence through GUI, accessibility-tree, file and database reads, marking requirements met, unmet or unknown. In online experiments it reduces false positives against baselines on AndroidWorld, OSWorld and ScienceBoard.

Research

GUI‑JEPA replaces token-by-token action decoding with candidate-conditioned latent scoring

Submitted October 27, GUI‑JEPA targets single-step mobile GUI action selection. It transforms JEPA representations pretrained on unlabeled interface screenshots for each action and region candidate, then scores accessibility-tree candidates in one batch instead of asking a 7B vision-language model to decode an action token by token.

Research

TAM turns verified task advancement into online state and reusable operations for GUI agents

Submitted October 27, Task Advancement Memory (TAM) uses what has been reliably accomplished at two timescales: it maintains verified progress, remaining goals and visual evidence during a task, then extracts reusable operations from locally successful segments after the task, including segments inside an overall failed workflow.