
What happened
Re-running the Zstd implementation eval with GPT-6 Astra, agents reached full test correctness over 99% of the time at $1 on medium effort, versus about 63% at $3.50 with GPT-5.6 Sol.
Why it matters
The jump in capability from 5.6 Sol to Astra means the benchmark is now saturated and a harder eval is needed, which suggests cheaper, more reliable coding agents.
WHO IT HITSSoftware teams using coding agents for test generation and implementation can expect higher correctness at lower cost with GPT-6 Astra, though the benefit on larger, harder tasks remains uncertain.
Summaries like this, every morning.
The original Zstd eval with GPT-5.6 Sol showed that asking agents to use specific testing techniques like TDD or QuickCheck often made them worse, and that not specifying any method produced many worthless unit tests but performed among the best. Re-running with GPT-6 Astra, the picture changed in two ways: capability rose enough to saturate the benchmark, and agents used test and verification techniques more effectively. For fuzzing, 5.6 Sol generated many worthless random inputs that hit the same code paths, while 6 Astra produced structured fuzzing that exercised code paths and found non-trivial bugs, though the Zstd benchmark is too easy to show whether that improved correctness. The author also tried the IMAP RFC, which was too hard for 5.6 Sol, and found that with 6 Astra the default condition once again looked pretty good, with some conditions giving somewhat better correctness at higher cost. Because the Pandoc eval only ran each condition 25 times at about $90k MSRP, the author cautions that the results have wide conceptual error bars and should not be over-interpreted. Still, several observations stood out: differential testing caused agents to examine boundary conditions and write tests that correctly implement both sides, TDD underperformed again, ACL2 performed well, and property-based testing libraries finally produced tests that do what one might hope. The author contrasts these findings with a viral claim that AI-written unit tests are empirically proven unhelpful, noting that claim was based on a 9% cost saving on smaller problems and that the DeepSWE grader penalizes test addition in ways not representative of real-world usage.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
On October 21, 2026, Anfini CEO Jun Hashimoto gave a special lecture at Meiji University's engineering faculty…

A six-year web designer who signed up for Claude Pro in April 2026 and later moved to Max published the first…

In one session that ran 13 days and 5,065 requests, a single request late in the session cost about $0.42 agai…

EC自動化工房 laid out four things to standardize before AI translation, using a sample mug "350ml" that mixed unit…

At WSJ Tech on Nov. 4, OpenAI president Greg Brockman said annualized revenue grew 70% in Q3 2026, with enterp…

Supasaito said it confirmed on November 4, 2026 that its listing appears in ChatGPT's directory, describing co…
