PrefDiag-Bench diagnoses how and when personalized GUI agents fail
Submitted October 22, PrefDiag-Bench uses 318 end-to-end tasks and 1,664 diagnostic probes to trace how preferences alter execution and when they should activate in GUI state; all 11 systems trail their own non-personalized baselines.
Why it matters
Generative and agent interfaces must do more than remember a preference: they must select the right historical evidence and activate it at the right interface state. Otherwise personalization becomes faulty automation at ranking, process or confirmation boundaries.
A closer look
The benchmark groups preferences into Outcome, Constraint, Ranking, Process and Interaction, comparing explicit profiles with behavioral-memory logs. The strongest system, Seed-2.0-Pro, scores 81.13% on basic tasks but averages 62.64% with profiles and 65.66% with logs; its Process score under profiles is 47.17%. On an 85-task subset, labeling logs as supporting evidence or noise raises Seed-2.0-Pro from 76.47% to 83.53%, while removing noise drops it back to 81.18%.
Who this is for
Teams building personalized agents, long-term memory, preference triggers, confirmation flows and GUI-automation evaluation
Original sources
- PrefDiag-Bench authors / arXiv and official repository ↗arxiv.org
- Full paper, results and limitations ↗arxiv.org
- Official code and data repository ↗github.com
Revisions & corrections (1)
— Paper, full text and official repository verify date, benchmark size, results and construction method; caveats preserve synthetic-context and intervention limits.