Case · DiggingBeagle record

VeriCUA verifies computer-using agents by exploring state instead of trusting screenshots

A verification system checks structured application state and selectively abstains, improving correctness on tested GUI-agent benchmarks at added cost.

Scope

Accuracy, abstention and cost are benchmark-specific; the study does not demonstrate production loss prevention.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade C
Remediation
not applicable
AI role
WITH AI
Basis and provenance

The pinned Claim and its primary disclosure support the described controlled result, but do not establish a population-wide rate or calibrated impact. The source is primary to the described analysis, not independent replication of every outcome. Impact remains unbanded because no calibrated impact rubric for this particular evidence is established.

Assessed Nov 2, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Agent performs GUI actions

    Clicks and text input produce a visible but potentially misleading page state.

    Boundary: User intent into application interaction

  2. 02

    Verifier gathers independent evidence

    A separate process inspects accessible structured state or receipts.

    Boundary: Visual appearance into durable application facts

  3. 03

    Decide or abstain

    The verifier labels completion only when its evidence supports it.

    Boundary: Observed state into user-facing success claim

Claims & evidence

CLM-2026-NOV02-VERICUA-STATE-VERIFICATION-AThe paper reports 90.5 percent AndroidWorld verification accuracy for VeriCUA versus 78.4 percent for a vision-language judge, with VeriCUA deciding on 82 percent of that sample.supported

Basis: reported finding

Link to claim
CLM-2026-NOV02-VERICUA-STATE-VERIFICATION-BIn the authors' AndroidWorld online evaluation, VeriCUA reached 90.5 percent overall accuracy with an 82 percent decision rate, versus 78.4 percent accuracy with 100 percent decisions for the VLM judge.supported

Basis: reported finding

Link to claim

Implications

Independent outcome verification is more reliable than trusting agent reports or screenshots alone, but abstention and measurement cost must be reported.

Controls and mitigations

  • Use app-level receipts, checked postconditions and explicit unknown status when protected state cannot be independently inspected.
  • Publish verification coverage, abstentions, false positives and cost together; verify a state-changing action against an application receipt rather than a screenshot alone.

Unknowns and contradictions

  • Accuracy, abstention and cost are benchmark-specific; the study does not demonstrate production loss prevention.
  • The results depend on benchmark instrumentation and structured state access; no customer transaction or safety-critical application validation is provided.

Sources and citation

Material revision history

  1. Nov 2, 2026 · Canonical change recorded · new in release · revision 214