Fetching from the wire…
Agents2026-07-10 · source-backed
arXiv 2607.07989 formalizes failure localization as its own research problem: identifying which agent is responsible and the exact step where the trajectory became irreversibly misdirected. Anyone running a fan-out of research or coding agents has lived this. The output is bad. The trace is 40,000 tokens. There's no obvious fault line. Treating this as a first-class problem rather than a debugging afterthought is overdue.
Each link below shares sources, entities, or timing with this story.
Every coding harness I've built, including the one that produces this newsletter, has some version of "if it fails, try again." That instinct is wrong, and there's now a study with the seed count to prove it. "Looping Is Not Reliability" (arXiv 2607.24604, July 27) runs a seal...
Skill files work because they're specific. They name the exact script, the exact API call, the exact flag your repo needs. That specificity is the whole value, and it's also the thing that quietly stops being true the moment the repo tags a new version. Repo2Skill-Evo measured...
Wu et al. name history reliability as a distinct failure mode: trace entries that stay structurally valid and semantically plausible after they stop being authoritative. On Qwen3-1.7B, polluted history flipped 32.1% of decisions correct under the original trajectory, usually v...
A June 26 paper (arXiv:2606.26294) describes a self-improving architecture where the agent and the evaluator that scores it evolve together, specifically to avoid the stagnation of optimizing against a fixed, gameable reward. (arXiv) Anyone building a self-improving harness ha...
Steve Yegge built a Go-based multi-agent orchestrator called Gas Town that ran 20 to 30 parallel Claude Code instances. It worked. Then it didn't. His postmortem, surfaced by Simon Willison on August 4, is blunt: Gas Town "fell apart at the seams with Opus 4.7. Up through 4.6...
RepoRescue tests coding agents on fixing a codebase broken by dependency and version changes across many files at once. That's a far more realistic and harder task than single-function bug fixing, and a better yardstick if you're deploying agents on legacy repos. Anyone who's...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.