Model comparison
Composer 2 vs SWE-1.7
Head-to-head evidence from 3 shared benchmark results across 2 categories. Overall scores shown here use BenchLM's provisional ranking lane.
Evidence parity. Composer 2 and SWE-1.7 share 3 comparable benchmark results. 1 of 8 categories are comparable. 2 results are unique to Composer 2; 1 to SWE-1.7.
Updated July 14, 2026- Shared results
- 3
- Composer 2 only
- 2
- SWE-1.7 only
- 1
- Comparable categories
- 1 / 8
Pick SWE-1.7 if you want the stronger benchmark profile. Composer 2 only becomes the better choice if its workflow or ecosystem matters more than the raw scoreboard.
Confidence note. This is a partial-evidence comparison with 3 shared benchmark results across 2 evidence categories; 1 of 8 categories currently have scoreable aggregates for both models. Treat the verdict as directional until coverage is more balanced.
Why this result
SWE-1.7 is clearly ahead on the provisional aggregate, 74 to 62. The gap is large enough that you do not need to squint at the spreadsheet to see the difference.
SWE-1.7's sharpest advantage is in agentic, where it averages 81.5 against 61.7. The single biggest benchmark swing on the page is Terminal-Bench 2.0, 61.7% to 81.5%.
SWE-1.7 gives you the larger context window at 256K, compared with 200K for Composer 2.
Category breakdown
Exact category averages are shown below. Not measured means BenchLM does not have enough sourced public coverage for that model and category.
| Category | Composer 2 | Δ | SWE-1.7 |
|---|---|---|---|
| Agentic | Composer 261.7 | Margin→ 19.8 | SWE-1.781.5 |
| Coding | Composer 258.0 | MarginNo overlap | SWE-1.7Not measured |
Decisive benchmark drivers
The largest measured benchmark gaps in this matchup, with exact reported values.
More
- Source ↗
Terminal-Bench 2.0
AgenticA 61.7%B 81.5%Winner: SWE-1.7Δ 19.8Terminal-Bench 2.0: Composer 2 scored 61.7%; SWE-1.7 scored 81.5%. SWE-1.7 wins this benchmark.
Operational comparison
Runtime and commercial metrics are compared only when both models have a complete sourced value.
| Metric | Composer 2 | SWE-1.7 | Comparison |
|---|---|---|---|
| Input / output priceUSD per 1M tokens | Composer 2$0.5 input / $2.5 output | SWE-1.7Not available | A complete price comparison is not available. |
| Generation speedtokens per second | Composer 2Not available | SWE-1.7Not available | A complete speed comparison is not available. |
| First-answer latencyseconds to first token | Composer 2Not available | SWE-1.7Not available | A complete latency comparison is not available. |
| Context windowmaximum listed tokens | Composer 2200K | SWE-1.7256K | SWE-1.7 lists the larger context window. |
Benchmark Deep Dive
AgenticSWE-1.7 wins1 benchmarks
| Benchmark | Composer 2 | SWE-1.7 | Result |
|---|---|---|---|
| Terminal-Bench 2.0Source | 61.7% | 81.5% | SWE-1.7 leads |
Frequently Asked Questions (2)
Which is better, Composer 2 or SWE-1.7?
SWE-1.7 is ahead on BenchLM's provisional leaderboard, 74 to 62. The biggest single separator in this matchup is Terminal-Bench 2.0, where the scores are 61.7% and 81.5%.
Which is better for agentic tasks, Composer 2 or SWE-1.7?
SWE-1.7 has the edge for agentic tasks in this comparison, averaging 81.5 versus 61.7. Inside this category, Terminal-Bench 2.0 is the benchmark that creates the most daylight between them.
Related Comparisons
Explore More
The AI models change fast. We track them for you.
A weekly brief for engineers and researchers covering new models, ranking shifts, and pricing changes.
Free. No spam. Unsubscribe anytime.