What is CursorBench?

CursorBench is Cursor’s own test of coding agents, built by tracing committed code in its editor back to the request that produced it and turning those requests into test cases. Cursor’s own technical report says CursorBench tasks run to a median of around 180 changed lines against 7 to 10 for SWE-bench, with prompts that are deliberately less specified, which is the company’s stated reason the two benchmarks don’t score the same model the same way.

Cursor hasn’t published how correctness is graded or how many tasks exist, and the tasks themselves are private, so nobody outside Cursor can check a result and Cursor also sells a model that’s scored on it. Terminal-Bench is one of the few independently maintained benchmarks that publishes both its method and its task set for the same kind of long, multi-file coding work, which makes it worth checking before trusting a CursorBench number on its own.

sources

keep reading

More on this.

Self-host Tessary.

Free and open source. Point it at the traces your agent already emits.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y