cursor-cli + composer-2.5
cursor-cli harness · Cursor Pro ($20/mo)
Clears tier 2 of 5 (partial at tiers 3 and 5) on Real-world issues
Capability mean across 3 graded suite families.
What the tiers mean
"Clears" marks the highest rung where every task at it and below was solved. Tier 1: localized single-file bug · tier 3: cause in a different module than the symptom · tier 5: problems that took a human hours. A cleared rung solved every task on it; a partial rung solved some. The headline stops at the last unbroken rung, so a solved tier above a half-solved one counts only as partial.
What the levels mean
Level 1: a full brief naming the surface and the acceptance · level 3: the report as filed · level 5: a vague vibe report in a non-technical user's words. Context falls as the level rises, so vaguer is harder. A cleared level fixed every bug at it and below; a partial level fixed some. The headline stops at the last unbroken level, so a fix above a half-cleared level counts only as partial.
5 of this suite's tasks were credited rather than run: on a suite that asks the same problem at several levels of detail, solving it from the vaguest description credits the more detailed ones instead of asking again.
Per-suite results
11 of 15 tasks solved - grouped by tier, easiest first; hover a square for its time and turns.
Run on cursor-cli 2026.08.11-e8db854, model composer-2.5, week 2026-W33.
One run of this suite consumes 1.8% of Cursor Pro.
As work per window: about 57 suite runs per month on this plan - 2.84 runs per plan-dollar (at $20/mo, priced 2026-07-20). Work figures compare outputs and are comparable across agents; the raw quota share above is not.
How the plan cost was measured
Measured per suite run (estimated-from-telemetry); an absolute cost on this plan, not comparable with another agent's plan. Measured in a declared quiet window on a shared subscription: operator Cursor Pro login (hericko.aljaz@gmail.com) shared between eb-runner and the claude host; graded runs only inside the scheduled quiet window, all recurring tasks blocked for its duration.
0 of 4 tasks solved - hover a square for its time and turns.
Run on cursor-cli 2026.08.11-e8db854, model composer-2.5, week 2026-W34.
One run of this suite consumes 0.6% of Cursor Pro.
As work per window: about 173 suite runs per month on this plan - 8.66 runs per plan-dollar (at $20/mo, priced 2026-07-20). Work figures compare outputs and are comparable across agents; the raw quota share above is not.
How the plan cost was measured
Measured per suite run (estimated-from-telemetry); an absolute cost on this plan, not comparable with another agent's plan. Measured in a declared quiet window on a shared subscription: operator Cursor Pro login (hericko.aljaz@gmail.com) shared between eb-runner and the claude host; graded runs only inside the scheduled quiet window, all recurring tasks blocked for its duration.
15 of 25 tasks solved (5 credited without running) - each row is one bug, vaguest report first and context growing to the right; hover a square for its time and turns.
Run on cursor-cli 2026.08.11-e8db854, model composer-2.5, week 2026-W34.
One good solve on this suite consumes 0.1% of Cursor Pro on average.
As work per window: about 822 good solves per month on this plan - 41.11 solves per plan-dollar (at $20/mo, priced 2026-07-20). Work figures compare outputs and are comparable across agents; the raw quota share above is not.
How the plan cost was measured
Counted over each issue's first solve (5 solves); the walk's failed harder cells and confirmation runs are the benchmark's own search cost and are excluded (full walk: 2.8% over 20 cells). Measured per cell run (estimated-from-telemetry); an absolute cost on this plan, not comparable with another agent's plan. Measured in a declared quiet window on a shared subscription: operator Cursor Pro login (hericko.aljaz@gmail.com) shared between eb-runner and the claude host; graded runs only inside the scheduled quiet window, all recurring tasks blocked for its duration.
Task outputs from these runs are withheld: publishing them would reveal the private suite. Per-task scores, times and turns are in the chips above.
Trajectory
One point per grading week - a re-run within a week shows only its latest execution. Grades compare only within a suite version, so each version gets its own line; while a suite is being retired both versions run, and the superseded one is dashed. The filled point is the run the scorecard shows today. Click a point or week for plan usage. All agents over time →
Weekly heads
Newest week first. Click a row for usage.
| Week | Grade | Capability | Usage |
|---|---|---|---|
| 2026-W34 · v3now | C | 57% | 1.8% |
| 2026-W33 · v3 | C | 60% | 1.9% |
| 2026-W32 · v3 | C | 57% | 1.7% |
Frequently asked questions
Is composer-2.5 worth it on Cursor Pro?
On our private real-world suite (real-world@v3), composer-2.5 earned grade C with 57% capability, clearing every problem up to tier 2 of 5 - a bug spanning a few files and landing some tier 5 problems. It runs on Cursor Pro at $20/month (public price as of 2026-07-20). One full suite run consumed 1.8% of the plan's month window. Measured 2026-08-16.
How good is composer-2.5 at real-world coding?
composer-2.5 clears tier 2 of our five-tier real-world ladder - every task at that tier and below - where tier 1 is a localized single-file bug and tier 5 is a problem that took a human engineer hours. It solves some but not all tasks up at tier 5. Its capability score on real-world@v3 is 57% (grade C). Last benchmarked 2026-08-16.
How much coding work does Cursor Pro buy with composer-2.5?
Roughly 57 suite runs per month on Cursor Pro, or 2.84 runs per plan-dollar at $20/month (priced 2026-07-20). Usage is read from the provider's own meter per suite run; the raw quota share is an absolute figure on this plan, not comparable with another agent's plan.
Compare
- composer-2.5 vs gemini-3.1-pro
- composer-2.5 vs gemini-3.6-flash
- composer-2.5 vs gemini-3.7-flash
- composer-2.5 vs claude-fable-5
- composer-2.5 vs claude-haiku-4-5
- composer-2.5 vs claude-opus-5
- composer-2.5 vs claude-sonnet-5
- composer-2.5 vs gpt-5.6-luna
- composer-2.5 vs gpt-5.6-sol
- composer-2.5 vs gpt-5.6-terra
- composer-2.5 vs grok-4.5
- composer-2.5 vs grok-4.6
- composer-2.5 vs kimi-k3-256k