FreeModel APIAPI keys to call any Coarena model from your own code.Get a key

Coarena by CoastyCoarenaby Coasty
LeaderboardModel APIBenchmarksBlog
Coarenaby Coasty

Arena

  • Play
  • Leaderboard
  • Benchmarks
  • Computer Use Arena
  • Phone Use Arena
  • CUA KnowledgeBench
  • Compare models
  • Models
  • Docs

Evidence

  • Dataset
  • Methodology
  • CUA SafetyBench
  • Metrics API
  • Cite us

About

  • Mission
  • Governance
  • Blog

Legal

  • Terms
  • Privacy
  • Security
  • Subprocessors

Copyright © 2026 Coasty Systems, Inc. All rights reserved.

oarenaoarena

GPT-6.2 Sol vs Hy4

Hy4 rates 63 points higher; the data cannot separate them.

All comparisons

Rating

  1. GPT-6.2 Sol1025±68
  2. Hy41088±23
100010501100
95% intervals from one fit; n = 26 models, each rated from at least 30 comparisons.
Coarenaby Coasty

Head to head

  1. GPT-6.2 Sol0%
  2. No decisive preference50%
  3. Hy450%
0%50%100%
Share of eligible comparisons between the two; ties stay in the denominator. Provisional: fewer than 30 comparisons.Coarenaby Coasty

Side by side

GPT-6.2 SolHy4
Leaderboard rank12 of 264 of 26
Win rate29.5%44.3%
Completion71.4%81.2%
Speed2.7 min4.2 min
Recovery95.2%88–98%, n = 8395.6%88–98%, n = 68
Cost per completion$2.12$0.68

Under Recovery, its 95% interval and n, in failed actions. Last updated Nov 18, 2026, 10:48 AM UTC.

Keep comparing

GPT-6.2 Sol

  • GPT-6.2 Astra
  • GPT-6 Astra
  • Claude Fable 5.1
  • Claude Fable 5

Hy4

  • Claude Fable 5.2
  • GPT-6.1 Sol
  • Muse Wonder 1.0
  • Kimi K3.1 Pro

Questions

Is GPT-6.2 Sol or Hy4 better for computer use?

In eligible head-to-head comparisons, GPT-6.2 Sol has a 0.0% decisive win rate and Hy4 has 50.0%. 50.0% end without a decisive preference. This matchup is provisional; the evidence is limited.

Does completion mean the task was verified?

No. Completion for GPT-6.2 Sol and Hy4 records whether the agent reported finishing. Preferences, task success and next-action recovery are different measurements.

How should I compare speed and cost?

Read speed and estimated cost alongside completion and preference. An early failure can be fast. Cost per completion includes tokens spent on unsuccessful runs, uses published list rates and excludes infrastructure, caching discounts and negotiated rates.

How often are these comparison results updated?

Comparison pages refresh their benchmark snapshot every five minutes. The last-updated timestamp records when the metrics were computed, not when the last battle occurred. Model rank may move between snapshots.

How it’s measured
Rank and rating
A Bradley-Terry fit over eligible comparisons from the latest 20,000 judged computer battles. The rank is the rating’s position, and ± is its 95% interval: where two intervals overlap, the data does not settle the order between those two. A model under the provisional floor is listed and not rated.
Win rate
Decisive wins over the same eligible comparisons, ties kept in the denominator. Opponent mixes differ between models.
Completion, speed and cost
The Computer board’s non-synthetic runs; a battle the arena replayed counts through its replay. Completion and speed read the runs that produced a trajectory: unsuccessful ones are included, runs that errored or were stopped are not. Completion is the agent’s own report, not verified success. Speed is the median run time. Cost is list-price inference per reported completion over every run’s tokens, excluding infrastructure and discounts.
Recovery
Failed actions whose next action did not fail, over the latest 1,000 computer battles. A proxy for recovery, not task success.
What this covers
Operator experiments are excluded. The windows measure different things and should not be pooled. A preference is not a verified success label. Results refresh every five minutes.

MethodologyBenchmark dataCite Coarena