Blolabel
← Notes
analysis 9 min read

Computer Agent Arena's 2,201 human votes reverse agent rankings that static benchmarks report; phoneshell's own static leaderboard failed a different way, it could not separate three models at all

A leaderboard can mislead in two different directions. It can confidently rank agents in an order a human user would reverse, which is what Computer Agent Arena measured. Or it can confidently fail to rank them at all, which is what a McNemar analysis found on phoneshell's own six-model board. Neither failure looks like the other from the outside.

Computer Agent Arena ("Toward Human-Centric Evaluation and Analysis of Computer-Use Agents," ICLR 2026, presented 23 to 25 April 2026 in Rio de Janeiro) is an open-source platform, built by a 19-author team including Bowen Wang, Tao Yu, Victor Zhong, Yi Zhang, Diyi Yang and Ion Stoica, that runs two anonymized agents head-to-head in matched, controlled cloud environments and collects human preference votes rather than relying on a fixed task-completion script. Across 2,201 high-quality votes over 12 agents, the paper reports "striking ranking reversals relative to static benchmarks." Overall correctness mainly drives human preference, but the authors find that agent-human interaction and self-correction also raise a user's preference even when overall task completion looks similar, and their error analysis names failure categories, long-horizon memory failures and fine-grained action failures among them, that the authors say static benchmarks do not evaluate.

Abstract technical illustration on a dark background of two separate ranking panels side by side: the left panel shows a sorted vertical list of markers with two positions swapped and highlighted, representing a reversed ranking; the right panel shows the same kind of vertical list but with three markers fused into one indistinguishable band, representing an absent ranking, cool blues and teals with one amber accent on the swap and one on the fused band

What changed, and when

Computer Agent Arena's critique of static benchmarks is about validity: a benchmark can produce a confident, statistically clean ranking that still does not match what a human user, watching the same agents work, would actually prefer. Its fix is to go get that preference directly, at scale, rather than assume task completion alone captures it. The platform and its 2,201-vote dataset are reported as open-sourced alongside the paper.

phoneshell's own leaderboard failure, documented in FINDINGS.md section 28, is about statistical power, a different axis entirely. Six models ran the identical 24-task public suite, a paired design, and a McNemar analysis of the pairwise disagreements found that three of the six, Claude Opus 4.8, GPT-5.1 and Qwen3-Max, were exactly symmetric: each won the same two tasks the other two lost. The published board had shown an 83.3% tie between them as if it were a ranking; the correct read is that the instrument could not tell them apart, and no size of sweep would change that, because there was nothing in the disagreement pattern left to scale. McNemar needs six one-directional disagreements to reach p < 0.05 regardless of sample size, and these three pairs never had more than two.

Reversed versus absent

dimensionComputer Agent Arenaphoneshellsource
what the static benchmark produceda confident rankinga confident-looking sorted list, actually unranked for 3 of 6 modelsproceedings.iclr.cc abstract; FINDINGS.md section 28
what the alternative measurement found2,201 human votes reverse that ranking for several agent pairsa McNemar exact test on the same data finds no significant separation to reverseproceedings.iclr.cc abstract; FINDINGS.md section 28
nature of the failurevalidity: the ranked property is not what users preferpower: the task set cannot statistically separate some models at any sizeproceedings.iclr.cc abstract; FINDINGS.md section 28
scale of evidence2,201 votes, 12 agents24 to 58 tasks, 6 models, 15 pairwise testsproceedings.iclr.cc abstract; FINDINGS.md section 28
fix applieda new, open-sourced human-preference platformWilson intervals, McNemar's exact test, and a power calculation added to every published boardproceedings.iclr.cc abstract; phoneshell/bench/stats.py
cross-check between the two failure modesnot reported, not phoneshell's datanever run: no human-preference vote has been collected on any phoneshell taskFINDINGS.md; not applicable to arXiv/ICLR source
Two different ways a leaderboard stops meaning what it says Computer Agent Arena: reversed static benchmark order 1. Agent A 2. Agent B 3. Agent C 2,201-vote order 1. Agent B 2. Agent A 3. Agent C A and B swap. The order exists on both sides; it disagrees. phoneshell: absent published board, sorted Opus 4.8 91.4% GPT-5.1 91.4% Qwen3-Max 89.7% McNemar: these 3 are statistically the same model Source: proceedings.iclr.cc/paper_files/paper/2026/.../Abstract-Conference.html; phoneshell FINDINGS.md section 28.
Computer Agent Arena's order disagrees with another order. phoneshell's order was never statistically there to disagree with in the first place.
Two axes a leaderboard can fail on, plotted together statistical separability (paired significance test) agreement with human preference low high low high reversed-ranking quadrant Computer Agent Arena's agents: separable, but reversed against human preference phoneshell's three tied models not separable at any sample size, preference agreement never measured ? Source: proceedings.iclr.cc abstract; phoneshell FINDINGS.md section 28. Axes are qualitative, not to scale.
The two results occupy different corners of the same two-axis problem. Nobody has yet placed a single leaderboard's models on both axes at once.

What it means for someone grading computer-use or phone agents

Both results point the same reader toward the same discipline, approached from opposite directions. Computer Agent Arena's lesson is that passing a validity check, agreeing with human preference, is a separate question from passing a statistical one, separating cleanly on a fixed task set; a ranking can be statistically tidy and still wrong about what matters. phoneshell's section 28 lesson is the mirror case: a ranking can look tidy, sorted percentages descending, and still carry no statistical content at all for part of the field, which is a problem a human-preference study would not even get the chance to contradict, because there was no real ranking there to compare against in the first place.

Neither project has run the other's check on its own data. Computer Agent Arena does not report, at least in what is available here, whether its reversed rankings would also fail a power analysis like phoneshell's McNemar test; and phoneshell has never collected a single human preference vote on any of its 80 tasks, so whether its device-state grades would agree with what a user watching the same run would prefer is simply unmeasured. A model that passes phoneshell's accessibility-tree check might still take an interaction path a human found clumsy, slow, or oddly phrased, properties phoneshell's binary pass or fail was never built to capture and Computer Agent Arena's whole platform exists to collect.

Check it yourself

# Computer Agent Arena's abstract and reported vote count
curl -s https://proceedings.iclr.cc/paper_files/paper/2026/hash/5f1d328711b162e1cf9896c7d6aaecdd-Abstract-Conference.html

git clone https://github.com/Blomega/phoneshell && cd phoneshell
grep -n "## 28" -A40 FINDINGS.md | head -60   # the three-way tie and the McNemar arithmetic
cat phoneshell/bench/stats.py                  # Wilson intervals, McNemar exact test, power calc, in one place
python3 scripts/run_sweep.py --help            # the resumable, round-robin sweep the fix produced

What would prove this wrong

Sources

  1. Wang, Yu, Zhong, Zhang, Yang, Stoica et al., "Computer Agent Arena: Toward Human-Centric Evaluation and Analysis of Computer-Use Agents," ICLR 2026, proceedings.iclr.cc, conference held 23 to 25 April 2026, read 22 October 2026. Also at OpenReview.
  2. Blolabel, FINDINGS.md, section 28, read 22 October 2026.
  3. Blolabel, phoneshell/bench/stats.py, read 22 October 2026.