Fetching from the wire…
Public story · 2026-08-23 · high
The model called the bug unsolvable, then produced a fix once Torvalds pushed back, in a commit landed August 22.
Why now: Torvalds' commit and Simon Willison's related note on verification both landed on August 22.
Linus Torvalds landed a Linux kernel fix on August 22 crediting an AI with doing much of the grunt work in what he called a debug session from hell. The commit stops the drm/xe graphics driver from handing out flat CCS storage as usable VRAM. In the message he writes that the model kept insisting the problem was impossible to solve, then kept adding diagnostic code anyway whenever he pushed back.
That's the detail worth sitting with. The usual complaint about coding agents is that they hallucinate fixes with confidence. This is the opposite failure. A model refused, confidently, and it was wrong to. Nothing in the refusal itself signaled that. Torvalds jokes that his own stubbornness outlasted the AI's training, but that's also the whole method: push once more before accepting "impossible."
Simon Willison made a related argument the same day. His claim is that the job isn't reading every line of a diff, it's confidently instructing an agent and confidently verifying the result, because line-by-line review was never the fastest way to catch a bad change. Torvalds' commit is what that looks like from the inside: instrumenting and re-checking instead of taking the model's first answer.
A Hacker News thread adds a rougher data point. Several people running Claude Code report worse outcomes on high reasoning effort than medium, including one case where a one-file config update turned into 43 minutes of pulling containers and building test suites. Anecdotal, unverified, but the shape matches. More compute spent isn't more judgment applied. Treat a model's "impossible" as a hypothesis, not a verdict, and go check it yourself.
Each link below shares sources, entities, or timing with this story.
Anthropic shipped cross-session messaging for Claude Code on August 7, macOS and Linux, version 2.1.224 or higher. Two new tools: ListAgents discovers other active sessions on your machine, SendMessage delivers text to one by name. Messages between sessions on the same machine...
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...
Spotify's Portal team published Xirp on August 10: a vendor-neutral agentic development environment that manages concurrent sessions across Claude Code, Gemini CLI, and Codex, each session isolated in its own git worktree so dozens of agents can work the same codebase without...
Fourteen times more commits. Not 14% more. 14x. GitHub COO Kyle Daigle dropped this number in a conversation covered by Simon Willison: the platform is currently running at 275 million commits per week, which annualizes to roughly 14 billion for 2026. In all of 2025, GitHub sa...
Issue 6235 on anthropics/claude-code asks Claude Code to read AGENTS.md, the config file that Codex, Amp, Cursor and most other harnesses already load, rather than only CLAUDE.md. It has been open since August 2025. It has accumulated over 5,200 reactions and 300+ comments, ma...
43.3% on Frontier-Bench v0.1. Opus 4.8 scored 18.7%. That's not an incremental bump, that's the same benchmark with a different shape of answer. Anthropic released Claude Opus 5 on July 24 at $5/$25 per million input/output tokens, exactly half of Fable 5's $10/$50, while matc...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.