Claude wins by a large margin * Claude Opus 4.6 : 0.71 * Claude Opus 4.5 : 0.51 * KIMI-K2.5 : 0.37 * GLM-5 : 0.36 * GPT-5.2 : 0.23 Note: later GPT versions seem to be only available within openAi's proprietary codex cli, so can't be tested - and if tested via the codex cli "harness" it wouldn't be a pure model-to-model comparison any more. --- Of course, the interesting follow-up question is: How well perform these m…
SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
21–30 of 49 posts
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#22Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#23Really long-term task benchmark showing significant improvements in very recent models, while also showing really bad regression rates across the board.
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#24Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#25[flagged]
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#26[flagged]
dang permaban this AI slop please
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#27I'm sure with benchmarks like these future LLMs will be optimized to hide regressions by "fixing" test framework too
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#28Claude wins by a large margin * Claude Opus 4.6 : 0.71 * Claude Opus 4.5 : 0.51 * KIMI-K2.5 : 0.37 * GLM-5 : 0.36 * GPT-5.2 : 0.23 Note: later GPT versions seem to be only available within openAi's proprietary codex cli, so can't be tested - and if tested via the codex cli "harness" it wouldn't be a pure model-to-model comparison any more. --- Of course, the interesting follow-up question is: How well perform these m…
Well that's already not a very fair comparison, we've known for years (one of the early-ish LLM papers, maybe someone knows which one) that prompting makes an enormous difference on agent performance, and most strikingly, the same prompt that massively boosts performance on one model, can massively reduce performance on another.
So you already need to fine-tune the prompts for the model, if you want anything approaching best results.
Now what's really amusing is that if you run models without their official harness, they can actually do way better on some benchmarks! [0] e.g. On Terminal Bench 2, Claude Opus 4.6 goes from #33 (Claude Code) to #5 (custom harness). Similar results for Codex.
Now, this is "for this one very specific benchmark", but I still thought it was funny, since you'd expect "the harness made by the same company" to be the best for all tasks, but that's clearly not the case. (For specific tasks, it's actually quite trivial to outperform a general purpose harness.)
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#29Claude wins by a large margin * Claude Opus 4.6 : 0.71 * Claude Opus 4.5 : 0.51 * KIMI-K2.5 : 0.37 * GLM-5 : 0.36 * GPT-5.2 : 0.23 Note: later GPT versions seem to be only available within openAi's proprietary codex cli, so can't be tested - and if tested via the codex cli "harness" it wouldn't be a pure model-to-model comparison any more. --- Of course, the interesting follow-up question is: How well perform these m…
Re: SWE-CI: Evaluating Agent Capabilities in Maintaining Codebases via CI
#30Unfortunately the paper doesn’t include gpt 5.3 which was released around the same time as opus 4.6 and also gpt 5.4 few days back. Both are available via api https://developers.openai.com/api/docs/models/gpt-5.3-codex IMHO The harness must be used when running these experiments. The model vendors know best on giving the best harness with gpt 5.4 and codex or Claude code with opus 4.6 which makes a big difference if…
This was only true for Claude Code for a while. Codex was poor and Gemini was unusable.
Since then Codex has gotten quite good.