There is no benchmark for the agent that merged your pull request.

Artificial Analysis launched a coding agent index last week that does something genuinely useful: it tests harness + model combinations, not just model weights. Same base model in Claude Code versus the same model in Cursor, scored separately. That is the right frame. Harness architecture drives more variance than model updates for most production workloads. But the benchmark tasks are good standardized tests, not your codebase. The benchmark claims "best combination." What a team needs is "which instance, for what work, on this specific repo." Benchmarks answer the market question: which configuration performs well on standardized tasks across the industry? The production question is different: which specific agent configuration, on my sessions, for my workflow types, has built a record that justifies routing? Most teams are using the first answer to make the second decision.} Food for agentic thoughts.