upvote
Okay, I wanted to know “which tasks” and dig into the methodology, and its documented nowhere!

A serious effort here would use a specific set of terminal bench questions. Instead these look like cherry picked questions. How were they picked and why? Without an answer we should assume they were picked to produce some result.

reply
Sorry for the inconvenience. We ran 27,280 total trials on Runta (1–4 vCPU, 2–8 GB RAM, 32 GB disk) using the 62-task frontier-harness-eval@v1.1.0 dataset across 5 models and 22 harnesses on Baseten, with 4 attempts per task. Every harness and model ran at max effort with a 131,072 max output token limit per request and per-task agent timeouts ranging from 15 minutes to 8 hours.

For scoring, final passes are divided by scored attempts, where infrastructure errors are excluded from the denominator, timeouts are still graded by the verifier, and reward hacking (such as looking up solutions online) counts as a failure. Costs are calculated using list price multiplied by reported tokens.

https://hub.harborframework.com/datasets/frontier-harness-ev...

reply
This doesn't answer the question at all.
reply
It's still the most informative thing to come out of that account or the linked article.
reply
For real, i remember setting up advanced Linux configurations back before the 3.0 kernel and I'm pretty sure I had a higher failure rate.

The biggest difference is that I, as a human, get mentally exhausted. but modern AI (when given unlimited tokens and tools) is like if Stephen hawking had a meth habit and the tenacity of Sisyphus with a bad case of syphilis after being told he can be cured if he can get that boulder over the hill

And even if they did try to test them on a lot of gotcha tasks; I'm perennially reminded of the ever-relevant quote about AI and other tech: "this is the worst it will ever be"

reply
That quote is outdated. My phone nags me now twice daily to update, and the update removes features I use so I'm careful to tread around it.

My Windows work desktop has two orders of magnitude more memory and more processing power than the last time I used Windows, yet boots slower and is laggier than any Windows I've ever used.

Almost all useful information online is concentrated into YouTube and Reddit, everything is advertising and trying to steal attention. I'm not even welcome on Reddit anymore due to the media campaigns against my country and race.

We've definitely passed the point where the derivative has gone negative.

reply
I'm also building a leaderboard in the meantime, which will release in a few days with more detailed harness version info and methodology.
reply
Confirmed. This is 17 TB4 tasks and 45 TB2.1 tasks. Why?
reply
We want to see how performance diverges between TB2.1 and TB4 while keeping costs manageable, since running the entire dataset is really expensive.
reply
How were the specific questions chosen?
reply
You can see the task in https://hub.harborframework.com/datasets/frontier-harness-ev...

We kept the category unified so we have tasks for every domain like ML , science and others.

reply
How were the specific questions chosen?
reply
Good finding! Model preference is interesting.
reply
Because these tasks are genuinely hard and require long-horizon reasoning, running full evaluation experiments gets expensive fast.

For example, on bun-sourcemap-leak (https://hub.harborframework.com/tasks/terminal-bench/bun-sou...), all 440 trials finished cleanly with zero infra errors or timeouts, yet 0 out of 440 passed all hidden-variant tests (the best was 35/36 across three DeepSeek V4.1 Flash runs).

Some of these tasks take up to 8 hours per run, so if you are not careful, you end up burning massive amounts of compute and API spend just to get an accurate evaluation signal.

reply
I wouldn't call it "burning of tokens and compute" if you get a useful signal out of it.
reply
Yeah exactly, compared to what baseline? People here will probably be stunned when I say this, but my pre-agent code was usually not bug free on my first attempts either.
reply
Over the 22 harnesses, the rank correlation of the steps per pass and the cost per pass was +0.51 (p = 0.015). For the other three factors, it was −0.03 to +0.02 (p ≥ 0.88). Within each model, tool calls tracked cost as well as steps. Table 4 below and Table 5 in the appendix give the values.

For harness developers: cut steps, not just prompt tokens. Prompt size, tool count and cache hit rate did not predict cost per pass. Steps did, because every step sends the whole context again.

Incredible, none of these harness developers considered just asking the LLM to solve the problem right away! Don't siege Leningrad, take it immediately!

reply
Cutting the system prompt and tools is easy. Cutting steps requires understanding the model's RL strategy and how it was trained to explore.
reply
I wonder if Claude Code would do better given they just introduced code mode, which should significantly cut the number of steps required
reply
Agreed. Does this help anyone decide what model or harness to use. Nope.
reply
[flagged]
reply