AI Update
Sunday, August 2, 2026

The Flywheel Turns Inward

Recursive self-optimization dropped the cost of frontier intelligence 13x in four months, an internal OpenAI model cracked ten decade-old math problems for pocket change, and the open-weights fight stopped being technical and got political.

The Big Picture

The headline this period isn’t a new model — it’s a new loop. OpenAI’s price cut on GPT-5.6 (Terra down 20%, Luna down a startling 80%) came with an unusually candid explanation: they pointed 5.6 Sol at its own forward pass, had it rewrite production Triton and Gluon kernels via Codex, and cut end-to-end serving costs roughly in half. Latent Space’s framing — the cost of GPT-5.4-level intelligence has fallen 13x in four months — is the number to sit with. The optimization flywheel that used to run through human engineers now partly runs through the model itself. If that compounds even weakly, the unit economics of everything you build shift under you every quarter.

Alongside the cost story, the “AI as working researcher” thread we flagged last week escalated hard. OpenAI set an internal version of its next model, Astra, on ten mathematics and theoretical CS problems with no progress in a decade — and shipped Lean 4 formalizations and a paper, reportedly for about $2,000 per problem at Sol prices. Coming days after Anthropic used Claude to find genuine cryptographic weaknesses, this is starting to feel less like a demo and more like a working instrument. Mathematicians online are having, in Simon Willison’s phrase, a collective Deep Blue moment.

And yet the money is nervous. Situational Awareness fell 67% in July’s rout, commentators are noting the AI trade now runs on borrowed money, and “After the AI Crash” made the front page. The dissonance — capability curves bending up while capital markets brace — is the defining tension of the moment. Falling inference costs are exactly what you’d want if you were worried about the bill.

Themes

The flywheel turns inward

The interesting part of the price drop isn’t the discount — it’s the mechanism. Distillation plus a model optimizing its own serving stack is a qualitatively different cost curve than “wait for the next GPU.” For you, two practical consequences: first, anything you priced out six months ago on token cost is worth re-pricing now, and Luna is cheap enough to be a sensible default (LLM 0.32 made it the out-of-the-box model). Second, the gap between “frontier” and “good enough and 10x cheaper” is closing fast enough that your model-selection logic should be revisited on a schedule, not set once.

Go deeper: How 5.6 fuses intelligence with efficiency · Distillation is all you need · Building abundant intelligence

AI as a working mathematician

This is the update to last week’s “AI as researcher” theme, and it’s a real escalation, not a re-run. The ten proofs come with formalized Lean artifacts and a reconstructed proof narrative — a decent transparency bar, though Willison rightly wants the prompts, and nobody’s saying how many problems yielded nothing. Hold it against Quanta’s sharp question — is the reasoning right for the wrong reasons? — and the shape of the next year comes into focus: the bottleneck moves from can it produce a result to can we verify one. Formalization (Lean) is quietly becoming the trust layer that makes machine-generated research legible.

Go deeper: Ten advances · Willison’s take · Right for the wrong reasons?

The open-weights fight goes political

Open weights stopped being an engineering debate and became a lobbying one. Microsoft shepherded Open Weights and American AI Leadership, signed by 235 companies — NVIDIA, Amazon, Y Combinator, the Linux Foundation, and (belatedly) OpenAI — explicitly to head off any government instinct to restrict open models on safety grounds. The technical case underneath it keeps getting stronger: DeepSeek-V4-Flash-0731 (304B, ~$0.14/$0.27 per million) may be the best value-per-intelligence model available right now, ranking above larger rivals; Mira Murati’s team released Inkling and Inkling-Small with a thoughtful staged-access safety framing; and Nathan Lambert’s read is blunt — the capacity to train strong models is proliferating. The counter-argument writes itself in the same letter: closed models are single points of failure that outsiders can’t audit.

Go deeper: Willison on the open letters · Open artifacts #23 · The Open Weight Revolution (Oxide podcast)

Frontier models on a laptop, one expert at a time

The most fun engineering story of the week came from r/LocalLLaMA, and it’s a real technique worth internalizing. Because sparse MoE models fire only a handful of experts per token, you don’t need the whole checkpoint resident — you keep the dense trunk and KV cache in RAM and stream the selected experts off NVMe on demand. One person ran Kimi K3’s 1.56TB checkpoint on a single CPU with 8GB of RAM (16 of 896 experts fire per token, read straight out of packed 4-bit); another got DeepSeek-V4-Flash 284B running in ~5.3GB at up to 4.8 tok/s on a 24GB M5. llama.cpp just landed MTP/DSpark support for V4-Flash, and there’s a serious hardware angle too — K3 runs at better perf-per-dollar on AMD’s MI355X than a B300. The takeaway: “too big to run locally” is increasingly a memory-bandwidth problem, not a parameter-count one.

Go deeper: K3 on 8GB · V4-Flash in 5.3GB · K3 on MI355X

MCP grows up: stateless 2.0

MCP had been quietly eclipsed by Skills — a shell and curl can do much of what MCP did, more flexibly — but the 2026-07-28 spec (informally MCP 2.0) has pulled Willison and others back in, and the reasoning is worth borrowing. Handing an agent a full terminal is powerful but risky and demands a strong model to drive it; MCP tools are auditable, controllable, and simple enough that small local models can use them reliably. Stateless MCP makes the servers far easier to deploy and scale. If your agent architecture has drifted all-in on shell access, this is a good moment to reconsider a tighter, inspectable tool surface — especially for the smaller models you’re now able to run locally.

Go deeper: Stateless MCP · llm-mcp-client · datasette-agent browser tasks · OpenSpace skill layer

Radar

Don’t Miss