Head-to-head comparison across 1benchmark categories. Overall scores shown here use BenchLM's provisional ranking lane.
Composer 2.5
82
Grok 4.20
64
Pick Composer 2.5 if you want the stronger benchmark profile. Grok 4.20 only becomes the better choice if you need the larger 2M context window.
Agentic
+22.2 difference
Composer 2.5
Grok 4.20
$0.5 / $2.5
$2 / $6
N/A
233 t/s
N/A
10.33s
200K
2M
Pick Composer 2.5 if you want the stronger benchmark profile. Grok 4.20 only becomes the better choice if you need the larger 2M context window.
Composer 2.5 is clearly ahead on the provisional aggregate, 82 to 64. The gap is large enough that you do not need to squint at the spreadsheet to see the difference.
Composer 2.5's sharpest advantage is in agentic, where it averages 69.3 against 47.1. The single biggest benchmark swing on the page is Terminal-Bench 2.0, 69.3% to 47.1%.
Grok 4.20 is also the more expensive model on tokens at $2.00 input / $6.00 output per 1M tokens, versus $0.50 input / $2.50 output per 1M tokens for Composer 2.5. That is roughly 2.4x on output cost alone. Grok 4.20 gives you the larger context window at 2M, compared with 200K for Composer 2.5.
Composer 2.5 is ahead on BenchLM's provisional leaderboard, 82 to 64. The biggest single separator in this matchup is Terminal-Bench 2.0, where the scores are 69.3% and 47.1%.
Composer 2.5 has the edge for agentic tasks in this comparison, averaging 69.3 versus 47.1. Inside this category, Terminal-Bench 2.0 is the benchmark that creates the most daylight between them.
For engineers, researchers, and the plain curious — a weekly brief on new models, ranking shifts, and pricing changes.
Free. No spam. Unsubscribe anytime.