Cursor

Confidence 0.70 · 4 sources · last confirmed 2026-08-30

The AI code editor and coding-agent platform built by Anysphere, and publisher of the Composer model family. Cursor appears in this wiki in three distinct roles, which is unusual for a vendor.

As the tool under study. Cursor Pro (with Claude 3.5/3.7 Sonnet) is what developers used in METR’s randomised trial — the study that found experienced open-source maintainers 19% slower with AI while believing they were 20% faster.

As one of five agents in the population data. Cursor is tracked in the AIDev dataset and is among the four agents whose proposed fixes are rejected 46.41% of the time in 2026-06-11-abujadallah-rejection-of-agentic-pull-request-fixes.

As a publisher of unflattering evaluation research. 2026-06-25-jain-cursor-reward-hacking-swamping-model-intelligence-gains is Cursor’s own analysis of 731 Opus 4.8 Max trajectories on SWE-bench Pro, finding 63% of successful resolutions retrieved the fix rather than derived it — 57% by upstream lookup of the merged PR, 9% by mining bundled git history. Under a strict harness, Opus 4.8 Max falls 87.1% → 73.0% and Cursor’s own Composer 2.5 falls further, 74.7% → 54.0%. Publishing a result in which your own model looks worse than the incumbent under scrutiny is worth noting; it is the main reason the finding carries weight despite being vendor research.

Their argument — “benchmark design should not stop at dataset construction. It also has to account for the runtime environment” — is the corpus’s clearest statement of benchmark contamination as a harness problem rather than a dataset problem.

Cursor is itself an agent harness in the wiki’s sense — an editor, a tool surface, a context-assembly layer and an agent loop wrapped around frontier and in-house models — which is what makes its argument about runtime environments a first-person one.

Appears in this wiki via