Skip to the comparison

DeepSeek V4.1 Flash (10/17) max vs Haiku 5.5 low

Haiku 5.5 low leads on speed and cost; DeepSeek V4.1 Flash (10/17) max has a slight edge on quality.

Quality
+3.5 pts
DeepSeek V4.1 Flash (10/17) max
Slight edge
3–0 head to head, 21 tied
Speed
3.8× faster
Haiku 5.5 low
9.9 min vs 37.2 min per task
Cost
4.4× cheaper
Haiku 5.5 low
$0.06 vs $0.28 per task

What this comparison is

  • 1 real repositoryStet-AI/stet, private; not public benchmark scores
  • 24 merged changeseach run end to end by the coding agent from the repo as it was before the change
  • Graded against the merged changeby the repo’s own tests and by judges comparing each patch with it
  • Quality, cost and timea smaller sample than public benchmarks, but real agent work on a real codebase

DeepSeek V4.1 Flash (10/17) vs Haiku 5.5: all effort pairings

24 tasksData from

Stet score

DeepSeek V4.1 Flash (10/17) maxcodex · max reasoningRank 11 of 18

48.395% range 42.9–53.43.5 points higher

Haiku 5.5 lowlow reasoningRank 16 of 18

44.895% range 39.0–50.1

A directional read: their 95% score ranges overlap.

Quality

Head-to-head matchups

DeepSeek V4.1 Flash (10/17) max won3

Tied21

Haiku 5.5 low won0

DeepSeek V4.1 Flash (10/17) max’s win share 57%, 95% range 49–65%Ties are within judge noise.

Task by task

DeepSeek V4.1 Flash (10/17) max solved 1 task that Haiku 5.5 low didn’t, and Haiku 5.5 low solved 1 that DeepSeek V4.1 Flash (10/17) max didn’t. Both solved 9; neither solved 11.

On the 9 tasks both solved, judges preferred DeepSeek V4.1 Flash (10/17) max’s patch on 2 and called 7 even.

1Only DeepSeek V4.1 Flash (10/17) max solved

  • 2 changed lines in 1 filestet-2450ca2dJudges preferred DeepSeek V4.1 Flash (10/17) max’s patch

1Only Haiku 5.5 low solved

  • 113 changed lines in 4 filesstet-commit-f0caded9

9Both solved

  • 4 changed lines in 1 filestet-43493c52Judges preferred DeepSeek V4.1 Flash (10/17) max’s patch
  • 6 changed lines in 1 filestet-3169aefa
  • 9 changed lines in 1 filestet-89dfbc27
  • 10 changed lines in 1 filestet-232b50ba
  • 23 changed lines in 2 filesstet-5276aa3f
  • 29 changed lines in 1 filestet-b28f4fe7
  • 84 changed lines in 1 filestet-66762b4cJudges preferred DeepSeek V4.1 Flash (10/17) max’s patch
  • 218 changed lines in 2 filesstet-commit-5d766dde
  • 941 changed lines in 7 filesstet-commit-bbbbae09

11Neither solved

  • 149 changed lines in 2 filesstet-commit-e928166f
  • 476 changed lines in 17 filesstet-commit-30506f8e
  • 481 changed lines in 3 filesstet-commit-5e075641
  • 552 changed lines in 11 filesstet-commit-60a0e6c2
  • 564 changed lines in 10 filesstet-commit-a8716b88
  • 640 changed lines in 8 filesstet-commit-342d0ac0
  • 763 changed lines in 8 filesstet-commit-87814583
  • 977 changed lines in 5 filesstet-commit-e41c2e2d
  • 1,236 changed lines in 16 filesstet-commit-d2ab0c25
  • 1,312 changed lines in 9 filesstet-commit-f8ae1177
  • 1,420 changed lines in 19 filesstet-commit-2826765e

Bar: changed lines in the merged change, log scale

A task counts as solved when its tests passed or a judge found the fix equivalent to the merged change, as in the leaderboard’s Solved column. Stet score also weighs code quality, so it can order the two differently. 2 of the 24 tasks are left out because one of the two has no scored result on them.

All 22 compared tasks
Task by task
TaskDeepSeek V4.1 Flash (10/17) maxHaiku 5.5 lowSolved byBetter patch
stet-3169aefa · 6 changed lines in 1 filePassed tests$0.06 · 15.9 minPassed tests$0.01 · 0.6 minBothEven
stet-89dfbc27 · 9 changed lines in 1 filePassed tests$0.05 · 4.9 minPassed tests$0.01 · 1.3 minBothEven
stet-b28f4fe7 · 29 changed lines in 1 filePassed tests$0.06 · 28.7 minPassed tests$0.02 · 3.4 minBothEven
stet-232b50ba · 10 changed lines in 1 filePassed tests$0.05 · 28.0 minPassed tests$0.01 · 1.1 minBothEven
stet-5276aa3f · 23 changed lines in 2 filesPassed tests$0.02 · 14.4 minPassed tests$0.01 · 3.6 minBothEven
stet-commit-bbbbae09 · 941 changed lines in 7 filesPassed tests$0.65 · 47.7 minPassed tests$0.05 · 5.9 minBothEven
stet-66762b4c · 84 changed lines in 1 filePassed tests$0.08 · 9.1 minEquivalent to the merged fix$0.01 · 2.9 minBothDeepSeek V4.1 Flash (10/17) max
stet-commit-5d766dde · 218 changed lines in 2 filesEquivalent to the merged fix$0.09 · 18.5 minEquivalent to the merged fix$0.03 · 3.7 minBothEven
stet-43493c52 · 4 changed lines in 1 filePassed tests$0.14 · 16.0 minPassed tests$0.01 · 0.8 minBothDeepSeek V4.1 Flash (10/17) max
stet-commit-f0caded9 · 113 changed lines in 4 filesFailed$0.09 · 14.6 minEquivalent to the merged fix$0.04 · 10.5 minHaiku 5.5 low onlyEven
stet-commit-f8ae1177 · 1,312 changed lines in 9 filesFailed$0.54 · 75.0 minFailed$0.17 · 12.0 minNeitherEven
stet-2450ca2d · 2 changed lines in 1 filePassed tests$0.07 · 10.1 minFailed$0.01 · 1.4 minDeepSeek V4.1 Flash (10/17) max onlyDeepSeek V4.1 Flash (10/17) max
stet-commit-342d0ac0 · 640 changed lines in 8 filesFailed$0.20 · 38.3 minFailed$0.05 · 32.1 minNeitherEven
stet-commit-60a0e6c2 · 552 changed lines in 11 filesFailed$0.34 · 39.2 minFailed$0.04 · 2.9 minNeitherEven
stet-commit-5e075641 · 481 changed lines in 3 filesFailed$0.46 · 53.1 minFailed$0.10 · 14.9 minNeitherEven
stet-commit-2826765e · 1,420 changed lines in 19 filesFailed$0.56 · 50.2 minFailed$0.19 · 13.8 minNeitherEven
stet-commit-a8716b88 · 564 changed lines in 10 filesFailed$0.30 · 40.2 minFailed$0.11 · 12.8 minNeitherEven
stet-commit-e928166f · 149 changed lines in 2 filesFailed$0.29 · 42.0 minFailed$0.04 · 3.3 minNeitherEven
stet-commit-30506f8e · 476 changed lines in 17 filesFailed$0.38 · 48.8 minFailed$0.19 · 30.4 minNeitherEven
stet-commit-87814583 · 763 changed lines in 8 filesFailed$0.50 · 62.2 minFailed$0.03 · 5.6 minNeitherEven
stet-commit-d2ab0c25 · 1,236 changed lines in 16 filesFailed$0.71 · 76.4 minFailed$0.36 · 50.2 minNeitherEven
stet-commit-e41c2e2d · 977 changed lines in 5 filesFailed$0.96 · 110.4 minFailed$0.03 · 11.9 minNeitherEven

Cost and time on each task

Each dot is one task, on a log scale: filled where the setup solved it, hollow where it didn’t. The line marks the median.

Cost per task

DeepSeek V4.1 Flash (10/17) maxmean $0.30 · median $0.25

Haiku 5.5 lowmean $0.07 · median $0.04

Haiku 5.5 low cost less on all 22 tasks.

Agent time per task

DeepSeek V4.1 Flash (10/17) maxmean 38.3 min · median 38.7 min

Haiku 5.5 lowmean 10.2 min · median 4.7 min

Haiku 5.5 low finished faster on all 22 tasks.

Where each setup is the better choice

The leaderboard’s readings on groups of tasks. Each group holds fewer tasks than the overall standings, so treat these as leads to test on your repo.

Small fixes

10 tasks · 2–84 changed lines in 1–2 files

DeepSeek V4.1 Flash (10/17) max solved 1 more, 8 of 8 to 7; Haiku 5.5 low cost 6.0× less per task.

Haiku 5.5 low was 8.5× faster.

Small fixes
DeepSeek V4.1 Flash (10/17) maxHaiku 5.5 low
Solved8/87/8
Cost / task$0.07$0.01
Agent time / task15.9 min1.9 min

Large, cross-cutting changes

Cheaper here without solving fewer: Haiku 5.5 low

14 tasks · 113–1,420 changed lines in up to 19 files

Haiku 5.5 low solved more, 3 of 14 to 2, at 4.2× lower cost per task.

Haiku 5.5 low was 3.4× faster.

Large, cross-cutting changes
DeepSeek V4.1 Flash (10/17) maxHaiku 5.5 low
Solved2/143/14
Cost / task$0.43$0.10
Agent time / task51.2 min15.0 min

Side by side

Side by side
MetricDeepSeek V4.1 Flash (10/17) maxHaiku 5.5 low
Harnesscodex—
Reasoning effortmaxlow
Rank11 of 1816 of 18
Stet score48.395% range 42.9–53.444.895% range 39.0–50.1
Solved10/249 passed, 1 judged equivalent11/247 passed, 4 judged equivalent
Cost / task$0.28$0.06
Agent time / task37.2 min9.9 min

Questions

Which is better for coding, DeepSeek V4.1 Flash (10/17) max or Haiku 5.5 low?
DeepSeek V4.1 Flash (10/17) max has a slight quality edge, 3–0 head to head with 21 tied; Haiku 5.5 low leads on cost and agent time: 4.4× cheaper and 3.8× faster. Measured on 24 merged changes from Stet-AI/stet.
How were DeepSeek V4.1 Flash (10/17) max and Haiku 5.5 low tested?
Both coding agents worked the same 24 merged changes from the private Stet-AI/stet repository, each in the real repo as it was before the change. The repo’s tests and judges graded every patch against the merged change; no public benchmark scores are used. Stet score: A setup’s average chance of beating another setup on a task, from 0 to 100; 50 is even with the field.

See which setup wins on your repo

Stet replays your merged changes, scores quality above pass/fail, and delivers comparison reports through your agent.

Get started