Fetching from the wire…
Public story · 2026-07-23 · high
It hits up to 76.1% pass@1 on four to six times fewer tokens than summarization, with the code public on GitHub.
Why now: The paper landed the same week a senior Anthropic engineer's graph-engineering thread went viral and Andrew Ng's team shipped a course on the same unbenchmarked idea.
PRO-LONG skips the summarization step every agent-memory system leans on, storing the full log instead and letting the agent grep it, per the paper.
That matters for anyone building agent memory. PRO-LONG beats a base coding agent by 18.0 percentage points across frontier models on the full ARC-AGI-3 public game set. It hits up to 76.1% pass@1 while spending 4.2 to 5.8 times fewer tokens than a summarize-and-evict setup. Run with Fable 5, it reaches 97.4% best@2 for $1,750 total. The code is public on GitHub.
The logic holds up once you sit with it. Summarization is lossy compression done before you know what you'll need. You're guessing at write time what'll matter at query time. Grep is lossless storage with retrieval deferred until the agent actually needs the answer. That's also where the token savings come from. You're not paying to re-read a summary every turn. You're paying only for the three lines you pulled out.
This landed the same week a senior Anthropic engineer's 12-page treatment of graph engineering went viral, four threads in 48 hours. It argues agent state needs an explicit typed node graph instead of a log. Andrew Ng's team shipped a course on the same idea days later. Turing Post is already running a piece asking if the whole thing is real. A definitive-guide post and a skeptic piece landing in the same stretch is what a hype phase looks like, not a settled one. PRO-LONG skipped that step and shipped a benchmark instead. A related paper, ContextSniper, points the same direction. Filtering verbose tool output cut Claude Code's tokens 38.9% on SWE-bench Lite tasks with resolution rates essentially unchanged.
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...
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...
A paper from Xiao Yu, Baolin Peng, and Ruize Xu makes a claim that seems obvious once stated and is genuinely new as a training methodology: modern agents are inseparable from their inference harnesses, so training them in stripped-down RL sandboxes produces a train/serve mism...
Here's the number that should change how you read every coding-agent ranking: 99 of 100 entries on the SWE-bench Verified leaderboard are vendor-submitted. One carries an independent verification badge. The other ninety-nine are labs grading their own homework on their own sca...
ARC-AGI-2 Reasoning Race. Gemini 3.1 Pro hit 77.1% and Claude Opus 4.6 hit 68.8% — both more than doubling their predecessors' scores in a single generation. The entire field moved ~10 points over the prior two years; each model jumped 30-40 points in one release. The top thre...
On April 10, Anthropic accidentally shipped 510,000 lines of TypeScript source maps with Claude Code v2.1.88 on npm. A missing .npmignore file. The community response was immediate and massive: someone created Claw Code, a Rust rewrite, which hit 50K GitHub stars in 2 hours an...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.