The blog itself can be seen more as an exploration of how speed impacts coding agent battle votes, than anything specifically about Neon.
Applying the speed impact to Gemini Carbon is particularly interesting, though, because it's the top model in our leaderboard when you exclude early votes (https://agentduel.com/leaderboard?excludeEarlyVotes=true) but mediocre when you let developers vote. Gemini literally takes 3x as long as opponents in matched battles.
But that's about as complicated as I get. I have recently tried to use Copilot because that is what work wants us to use, and even with Opus 5.5 it is noticeably inferior to CC on the same model. Wild. So clearly the harness matters.
For what it’s worth, the linked article data (Agent Duel data) is all run on OpenCode. I’m curious if people would prefer we run each model in its native harness (at the expense of user experience because it’ll be buggy).
- SWE-bench Pro (hard 51): 39.2% → 64.7%
- Terminal-Bench 2.1: 39.5% → 55.8%
If this were true, models would do way better in their own harness than in others, which doesn't seem to be the case (effect is minor).
Your link has a "link to the release blogpost" which is supposed to explain the training recipe but the link is down.
My company is slow-walking (and that is an understatement) our LLM usage, so the majority of work that I'm reviewing is human generated. After the stories I hear of what other people are experiencing when management is more enthusiastic, maybe I should count myself lucky.
"OK, google models perform just as well, are faster and are cheaper but all that doesn't matter. Because the models, now that Google has very good ones, doesn't matter after all. All that matters is the harness".
And of course it's upvoted by the Anthropic shills.
Second, I will be trying this with agy when my Opus 5.5 limit hits. I only hope its faster than Argon which is already dog slow
For this model, I mean. And not the Anthropic IPO.
Just as good but cheaper comes from the benchmark performance. Also faster from openrouter. The opus 5.5 parity projection is an internal model based on those assumptions from the Agent Duel team.
We’re reaching the point where certain models are really good at 1 thing. The person writing this blog post isn’t using Neon for large-scale orchestration, but I’m sure it excels in its usage. For me Fable 5.2 as the orchestrator and Opus 5.5 and grunt workers have led to the most robust software...so far.
I'm the person writing this. This is head to head battle data by real developers on top of OpenCode. The data is generated by an open source app so you can inspect it yourself (https://github.com/bottomless/agent-duel). The hitch is there's no real Neon data. This is purely projecting from Carbon's super slow but very good performance onto Neon's likely fast and likely equal performance.