Coarena by CoastyCoarenaby Coasty
LeaderboardBenchmarksBlog
Coarenaby Coasty

Arena

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

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

Claude Sonnet 5.5 vs DeepSeek V4.1 Flash 1017

Claude Sonnet 5.5 rates 87 points higher; the 95% intervals do not overlap.

All comparisons

Rating

  1. Claude Sonnet 5.5970±27
  2. DeepSeek V4.1 Flash 1017883±55
850900
950
95% intervals from one fit; n = 21 models, each rated from at least 30 comparisons.

Head to head

  1. Claude Sonnet 5.514%
  2. No decisive preference0%
  3. DeepSeek V4.1 Flash 101786%
0%50%100%
Share of eligible comparisons between the two; ties stay in the denominator. Provisional: fewer than 30 comparisons.

Side by side

Claude Sonnet 5.5DeepSeek V4.1 Flash 1017
Leaderboard rank16 of 2121 of 21
Win rate29.2%17.8%
Completion91.5%97.3%
Speed38.4 s53.4 s
Recovery77.8%45–94%, n = 991.4%78–97%, n = 35
Cost per completion$0.187$0.132
Phone rank9 of 2016 of 20

Under Recovery, its 95% interval and n, in failed actions. Last updated Nov 5, 2026, 10:43 PM UTC.

Keep comparing

Claude Sonnet 5.5

  • GPT-6 Luna
  • Muse Spark 1.3
  • Gemini 3.8 Flash
  • Claude Haiku 5.5

DeepSeek V4.1 Flash 1017

  • Kimi K3
  • MiMo V2.6 Pro
  • GLM 5.3 Flash
  • MiniMax M3.1 Flash

Questions

Is Claude Sonnet 5.5 or DeepSeek V4.1 Flash 1017 better for computer use?

In eligible head-to-head comparisons, Claude Sonnet 5.5 has a 14.3% decisive win rate and DeepSeek V4.1 Flash 1017 has 85.7%. 0.0% end without a decisive preference. This matchup is provisional; the evidence is limited.

Does completion mean the task was verified?

No. Completion for Claude Sonnet 5.5 and DeepSeek V4.1 Flash 1017 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.
Phone
Phone rank is each model’s place on the Phone board’s own fit over phone battles, of the models that board ranks. Some phone comparisons are judged by a model, not a person: GPT-6 Astra, or another model on battles it plays in, reads both runs twice with the sides swapped and names a winner only when both readings agree, otherwise a tie. Up to 2026-10-25 the model judge also read each task’s key and, where the task checks one, each phone’s final state, which no person judging is shown. When it was itself one of the two contestants, it called a tie every time.
What this covers
Operator experiments are excluded. Every phone battle rated up to 2026-10-25 came from our own campaign: we wrote the tasks and planned the pairings for coverage. 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