Fetching from the wire…
Public story · 2026-08-10 · high
Broad exploration of variations helped tuning gains; reading traces closely to find bugs hurt them, per Scale AI's benchmark.
Why now: Both findings landed on August 10, the same day Prime Agent hit 12,520 stars and No. 6 on Product Hunt.
Upgrading the optimizer model beats rewriting the harness by 1.8x on held-out test scores, per Scale AI's new HarnessOpt-Bench.
That's a 0.142 average score move from swapping the optimizer model, versus 0.079 from swapping the harness. Check the optimizer first, before spending an eval budget on scaffolding rewrites.
The behavioral finding is stranger. Broad exploration of the solution space correlated positively with gains, Spearman +0.34 to +0.88. Reading agent traces closely to hunt for the one bad tool call correlated negatively, -0.31 to -0.64.
Case-pass budgets bound the work harder than eval-call budgets too: 82% median utilization against just 4%.
I've burned entire evenings reading traces line by line looking for the failure. This paper says that time cost more than it returned. I'm not fully sold, trace-reading is usually how I find the hypothesis worth testing.
The same day, PrimeIntellect-ai/prime-agent picked up 2,655 GitHub stars. That's about 3x the next-fastest repo on GitHub Trending, and it landed at No. 6 on Product Hunt.
Its pitch is a Continual Harness that edits its own prompts, skills, and subagent specs mid-run, built on a Recursive Language Model architecture. Prime Intellect claims 95.5% Best@1 on ARC-AGI-3 with Opus 5, edging a 95.4% human-expert baseline.
A related paper, ADIAS, backs a narrower version of the same idea. It carries a persistent issue list across optimization rounds instead of re-diagnosing from scratch each round. That's worth a 25.2% average improvement, and removing it drops performance up to 40.7%.
Each link below shares sources, entities, or timing with this story.
Everyone spent yesterday arguing about benchmark numbers. Tencent quietly published data suggesting the numbers belong to your infrastructure, not the model. The WorkBuddy Bench leaderboard reports every model under two different agent harnesses — CodeBuddy Code and Claude Cod...
Terminal-Bench 2.1 results (entries dated June 17) put Codex CLI on GPT-5.5 first at 83.4%, Claude Code on Fable 5 second at 83.1%, and Claude Code on Opus 4.8 at 78.9%. The asterisk matters more than the ranking: Fable 5 and Mythos 5 have been export-suspended since June 12,...
Writer launched Palmyra X6 on August 13 with a number that should reset how you think about agent COGS: 52% lower average cost, 48% better speed, 10% better quality. The model is a post-training variation of Z.ai's open-source GLM-5.2. A US enterprise SaaS vendor built its fla...
Moonshot AI dropped Kimi K2.6 today and the numbers are hard to ignore. One trillion parameters total, 32 billion active per token across 384 experts, 256K context window, and native multimodal input. It scores 58.6 on SWE-Bench Pro versus GPT-5.4's 57.7 and Claude Opus 4.6's...
Claude Code 2.1.229 shipped a config flag most people will scroll past: CLAUDE_CODE_WORKFLOW_PREFIX_STAGGER_MS. What it does is delay the launch of sibling agents that share a prompt prefix, so the second through Nth agents read the warm cache instead of each writing their own...
Open-sourced under MIT, built on two abstractions: a Recursive Language Model (a persistent IPython REPL where the model calls sub-agents as functions, keeping programmatic access to context and history) and a Continual Harness treating its own prompts, skills, memory and sub-...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.