87 points Edward40 1 hour ago 32 comments
guanlan 1 hour ago | parent
The short version: when you change the model, think about changing the harness too. On any one model, cost per pass varies by up to 4.4x
What we ran: 22 harness configurations × 5 open-weight models × 62 terminal tasks × 4 attempts. 27,280 runs, 83B tokens. Each harness ran with default settings at maximum reasoning effort, each trial in a fresh sandbox. Costs are Baseten list prices times reported tokens.
What we found: The lowest-cost harness changes with the model. Codex CLI ranks 1st on cost with GLM-5.3 and 15th with Kimi-K3. Paying more doesn’t buy passes. The harness with the highest pass rate ranked anywhere from 4th to 19th on cost. The model still sets most of the bill (93% of cost variation). The harness is the second lever. Starting prompt size doesn’t predict cost. Output tokens do. 64% of inference spend went to runs that didn’t pass.
radlad 58 minutes ago | parent
> Don't post generated text or AI-edited text. HN is for conversation between humans.
latentsea 38 minutes ago | parent
Majromax 42 minutes ago | parent
The 'steps per pass' criterion is also not something under the harness's direct control in the way that its tool collection and system prompt (/start tokens) are. Even the cache hit rate is hard to control beyond a limit, since modern harnesses rarely rewrite history.
I'm also suspicious about the run-to-run variance between models. Given the high variability within the presented results and the observation that failed runs (which can spin for a long time before delivering a wrong answer) account for a majority of the cost, I'm not sure that many of the conclusions here would hold up under a second sample.
Zigurd 35 minutes ago | parent
embedding-shape 31 minutes ago | parent
Otherwise you still end up with balls of spaghetti where each change takes longer and longer to work into the codebase. With a bit of planning, you can keep tackling changes and they keep taking the same amount of time more or less.
smallnamespace 25 minutes ago | parent
The requirements will be more stable than the code. Focus on them instead.
catdog 16 minutes ago | parent
Wouldn't count on it. There likely is a ceiling, we might or might not be near it.
datsci_est_2015 15 minutes ago | parent
Zigurd 13 minutes ago | parent
These kinds of changes to the way teams are formed and managed, and how products are developed is what really fascinates me about the impact of coding agents.
Even if it works, for some definition of works, to dump a huge spec into a coding agent context window, I suspect this is where a lot of horror stories about agentic coding come from.
Teams, and the management structure above them, are going to have to get used to more collaborative and iterative product definition and development in order to extract the most value from coding agents.
rrr_oh_man 28 minutes ago | parent
I find that only works with topics I know very little about.
datsci_est_2015 17 minutes ago | parent
- tongue in cheek: in topics you know very little about, you don’t have the ability to tell whether the LLM output is trash or not
- very serious: LLMs allow you to create things you could not have created before due to not having the knowledge
Sort of like a Dunning-Kruger or Gell-Mann amnesia.devmor 9 minutes ago | parent
LLMs are allowing people to create things with very little effort compared to before, and those creations are of questionable quality - indeterminable by the LLM-user due to a lack of experience.
contravariant 16 minutes ago | parent
The places where you let an agent do its thing is bound by the (implicit) interface your prompt creates. In an ideal situation this interface is a simple isolated thing in your application.
If you just let it do its thing, expect a monolith. You shouldn't rely on it coming up with interfaces that mesh well with what you had in mind, and each of those interfaces represents a decision that it took, restricting future iterations of the code. So a monolith is not only what you can expect, but also the best you can hope for.
If you want to let it cook, create more places for code that does a thing and you don't care how.
Ericson2314 13 minutes ago | parent
The "objective" nature of code is revealing a flaw in the human division of labor.
cronin101 25 minutes ago | parent
Can anyone confirm/deny this is the case?
If so, it seems a shame not to include this practice into the reporting methodology for full transparency.
jrmg 21 minutes ago | parent
cronin101 18 minutes ago | parent
As with most post-training this would be done via some scored/verifiable problem set (we can probably tell if the tool calls blew up during the coding trajectory) e.g. a known set of input tasks where solutions can be verified.
Last-mile aka doing in yourself (on box) vs the compute cluster that created those open weights.
https://en.wikipedia.org/wiki/Fine-tuning_(deep_learning)
I believe (at least this used to be the case) that heavily quantized models that are designed to fit on consumer hardware have inflated failure rates and this can claw back quite a bit of reliability.
ford 15 minutes ago | parent
cronin101 10 minutes ago | parent
However, the hardware requirements are still quite enormous.
I could see a gap in the market for crowdfunded (gofundme?) post-training of open-weight models, per harness. I estimate that the one-time compute cost is probably $x000 so this scales nicely with a large number of interested developers that could reuse the weights.
jrmg 21 minutes ago | parent
The page's title is: "Introducing FrontierHarness Eval v1.1"
ford 18 minutes ago | parent
scubazealous 15 minutes ago | parent
seizethecheese 11 minutes ago | parent
It’s unclear whether that’s supposed to be surprising against the selected models for the benchmark. I suspect it’s not and the headline is written to pander to “wasting money on AI” upvotes.
andai 8 minutes ago | parent
I've seen this for years, and seen several papers that studied it: the same prompt will help with one LLM and harm performance for a different LLM on the same task.
And on benchmarks which test LLM x Harness, they find that LLMs tend to do way better with their "own" harness. (Or in the case of Chinese LLMs, the harness of the LLM whose training data they borrowed :)
shevy-java 8 minutes ago | parent
colinmarc 6 minutes ago | parent