Composer 2.5 scores D overall on Electricity Bench and clears tier 1 of 5 on real-world issues. Its best suite is spec planning at D. One pass of our task set uses 2.0% of Cursor Pro's monthly limit. In our own use it has no clear role right now.Measured
"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.
Clears level 1 of 5 (partial at levels 2, 3, 4 and 5) on Vibe coding v1 - the vaguest report level at which it still fixed every bug, having also cleared every richer level below
12345
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.
3 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.
10 of 15 tasks solved - grouped by tier, easiest first; hover a square for its time and turns. solved partial not solved
Run on cursor-cli 2026.09.26-dd393fe, model composer-2.5, week 2026-W40.
One run of this suite consumes 1.6% of Cursor Pro.
As work per window: about 63 suite runs per month on this plan - 3.15 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 on a shared personal subscription during a quiet window, not a dedicated bench login.
0 of 4 tasks solved - hover a square for its time and turns. solved partial not solved
Run on cursor-cli 2026.09.26-dd393fe, model composer-2.5, week 2026-W40.
One run of this suite consumes 0.4% of Cursor Pro.
As work per window: about 225 suite runs per month on this plan - 11.23 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 on a shared personal subscription during a quiet window, not a dedicated bench login.
10 of 25 tasks solved (3 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. solved partial not solved credited
Run on cursor-cli 2026.09.26-dd393fe, model composer-2.5, week 2026-W40.
One good solve on this suite consumes 0.1% of Cursor Pro on average.
As work per window: about 920 good solves per month on this plan - 46.02 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.4% over 22 cells). Measured per cell run (estimated-from-telemetry); an absolute cost on this plan, not comparable with another agent's plan. Measured on a shared personal subscription during a quiet window, not a dedicated bench login.
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 →
Put Composer 2.5's current grade in a README or a docs page.
Markdown
[](https://electricitybench.com/models/cursor-cli-composer-2-5/)
HTML
<a href="https://electricitybench.com/models/cursor-cli-composer-2-5/"><img src="https://electricitybench.com/badge/cursor-cli-composer-2-5.svg" alt="Composer 2.5 on Electricity Bench: D"></a>
Badges update every Monday with the weekly run. GitHub renders them from this URL.
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 1 of 5 - a localized single-file bug 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.6% of the plan's month window. Measured 2026-09-27.
Is Composer 2.5 good for coding?
Composer 2.5 clears tier 1 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-09-27.
How many coding tasks do you get with Composer 2.5 on Cursor Pro?
Roughly 63 suite runs per month on Cursor Pro, or 3.15 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.
How much of Cursor Pro does one Composer 2.5 task use?
One full suite run consumed 1.6% of Cursor Pro's monthly limit, read off the provider's own meter before and after the run. A benchmark task is a whole multi-turn agent session, not a message, and the share belongs to this plan alone: it is not comparable with another agent's plan. Measured 2026-09-27.
