Fetching from the wire…
Public story · 2026-08-04 · high
A deterministic wrapper adds zero extra LLM calls, cutting GPT-5 mini's SWE-bench cost 28.9% while lifting accuracy, per the study's 500-instance benchmark.
Why now: The paper and two companion studies on agent context spending all surfaced in the August 4, 2026 briefing.
A runtime wrapper called Ledger raised GPT-5 mini's SWE-bench Verified pass rate from 56.2% to 64.2% while cutting total cost 28.9%, according to a paper posted to arXiv.
The result isn't a cherry-picked subset. It's all 500 SWE-bench Verified instances, and the gain held on a second model: MiniMax M2.5 went from 75.8% to 81.0% with cost down 31.8%. Plugged into OpenAI Codex, Ledger added 3.4 points at 24.4% lower cost.
Ledger doesn't touch the agent itself. It tracks what's been observed, modified, and attempted across a session. Then it acts on that record at two points.
The inform path appends a compact state summary to the prompt. The govern path checks each proposed command against the ledger. If a result's still valid, it hands that back instead of letting the agent re-run the command, and flags the repeat. Neither path costs an extra model call.
The paper's ablation splits the credit cleanly: govern drives most of the accuracy gain, inform drives most of the savings. That's useful if you're deciding which half to build first.
A companion paper tested prompt wording across six models. Asking a model to develop and compare several approaches alone multiplies reasoning-token spend 2.4 to 7.4 times. A bounded prompt, stating scope and a stop condition, is cost-neutral and can cut reasoning roughly in half.
Wix's Helpmate found a similar pattern in skill selection. Filtering by what an account can actually execute, rather than by relevance, cut context 90.5% across 756,600 messages. Replaying 1,000 risk-enriched conversations with everything exposed, the model picked a production-blocked skill 7.8% of the time.
I'm building the govern path next.
Each link below shares sources, entities, or timing with this story.
This is the paper of the week. arXiv 2607.28871 introduces BSG-VA, which replays every validation command an agent runs across three code states: the original buggy code (B), the candidate patch (S), and the gold developer fix (G). If a test passes in all three states, it neve...
Accuracy drops 30–50% well before you hit the documented context limit. Not at the limit. Before it. Cross-model testing across GPT-4.1, the Claude 4 family, Gemini 2.5, and Qwen3 quantified what everyone shipping long-context features has felt and couldn't measure (Glasp). Th...
The standard multi-model coding pipeline uses a reasoning model to plan, then a code specialist to generate. A new paper flips the pattern — let the specialist generate freely, then have the reasoning model review — and hits 90.2% pass@1, outperforming GPT-4o at 87.2% and O1 P...
Here's the experiment: a team of cooperating agents rebuilds SQLite in Rust from scratch, using only the 835-page manual. No source code. No test suites. No internet. Then it has to pass a held-out sqllogictest suite. It worked. Cursor published the research (Wilson Lin, July...
DeepSeek dropped V4 in mid-June as an open-weight model with a 1-million-token context window, priced at $1.74 per million input tokens, posting near-parity with GPT-5.4 on math and Q&A benchmarks (MindStudio). That's the headline number. The architecture underneath is more in...
The winner isn't the story. The methodology is. Databricks published its internal coding-agent benchmark: real engineering tasks pulled from its own multi-million-line codebase spanning Python, Go, TypeScript, and Scala. Roughly 25% low-complexity tasks, about 60% medium. Not...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.