Anthropic's Fable 5 is back online after 18 days dark. Zhipu's GLM 5.2 landed within 1 point of Opus 4.8 at a fifth of the cost. Mistral solved 587 of 672 Putnam problems with an open model. And three separate teams shipped agents that can read — your browser, your webpage, and your Fitbit. Here's everything.

Fable 5 and Mythos 5 are back online worldwide as of July 1, after the Commerce Department's export control order — triggered by a reported jailbreak — was lifted on June 30. Anthropic shipped a new classifier specifically targeting the flagged technique before flipping access back on.

So what: 18 days dark is a real cost for any team that built around Fable 5. The bigger takeaway: a single reported jailbreak can now pull a frontier model globally within days — plan your model dependencies accordingly.

TwoTower is a block-wise autoregressive diffusion model adapted from NVIDIA's Nemotron-3-Nano-30B-A3B hybrid Mamba-2/attention backbone — instead of training a diffusion LM from scratch, NVIDIA repurposed an existing autoregressive checkpoint into a two-tower diffusion architecture.

So what: Diffusion LMs promise parallel token generation (speed), but training one from zero is expensive. Bootstrapping off an already-trained AR model is a much cheaper path to diffusion-style inference — expect more labs to copy this recipe.

Leanstral 1.5 (119B-A6B) is Mistral's Lean 4-specialized theorem-proving agent, fully open under Apache 2.0. It solves 587 of 672 PutnamBench problems — competition-level math formalized in Lean 4 — putting it ahead of comparable open baselines without natural-language guidance.

So what: Formal verification is the missing piece for trustworthy "vibe-coded" software and math. An open, Apache-licensed model this strong at Lean 4 lowers the bar for teams to build verified-correct code and proofs into their own pipelines.

WebBrain is a free, MIT-licensed browser agent that runs inside your existing authenticated Chrome or Firefox session — no separate login, no headless browser, no API key hijinks. Point it at any model you already have access to, and it reads pages, extracts data, and automates multi-step tasks directly in your real browser tab.

TabFM reads an entire tabular dataset as a single in-context prompt and performs classification and regression zero-shot — no dataset-specific training or fine-tuning required. It uses a hybrid-attention architecture built specifically for structured/tabular data, with weights open on Hugging Face.

So what: Most production tabular ML is still XGBoost plus hours of manual feature engineering per dataset. A foundation model that does in-context learning on raw tables — the same way LLMs do in-context learning on text — could collapse that workflow into a single zero-shot call.

AI, Explained Simply

The Universal Plug for AI (a.k.a. why everyone's suddenly saying "MCP")

Quick question: do you have a drawer full of tangled chargers at home? One for your phone, one for your old camera, one for that random Bluetooth speaker?

That drawer is basically how AI used to work with your tools — email, databases, Slack, whatever. Every connection was custom-built, one at a time. Today I want to show you the thing that fixed it. It's called MCP (Model Context Protocol), and once you get it, you'll understand why every AI company suddenly can't stop talking about it.


The problem, first

Say a company wants their AI assistant to read email, check a database, and post in Slack. The old way: build a custom connection for each pair. Then they get a second AI tool. Guess what — they have to rebuild all those connections again, from scratch, just for the new one.

This is sometimes called the M×N problem: M assistants times N tools equals a growing pile of one-off wires. Nobody wants to be the person maintaining a hundred custom cables.

Analogy: before USB-C, every phone, camera and laptop had its own charger shape. You needed a whole drawer of cables. USB-C said: one plug shape, any device, any port. MCP is that idea — but for AI and the tools it uses.

How it actually works

Two simple pieces:

  • MCP server — a small adapter someone builds once for a tool (Gmail, a database, your files, whatever). It exposes what that tool can do in a standard format.
  • MCP client — lives inside the AI itself. It doesn't need to know anything special about Gmail vs. Slack vs. a database — it just speaks the same standard language to all of them.

Because both sides agree on the same "plug shape," any MCP-capable AI can use any MCP server, instantly. Build a server once — every AI benefits, not just the one it was built for.

The "aha" moment

Before MCP: a company wanting both Claude and ChatGPT to read their internal database had to build two separate custom integrations.

With MCP: they build the connector once, and it works for both — same way any USB-C cable works in any USB-C port, no matter the brand.

MCP is the USB-C of AI.
One standard plug, so any AI can use any tool — instead of everyone building their own one-off cable.

That's really the whole idea. Everything else — the JSON configs, the server code — is just implementation detail on top of this one insight.

Got a concept you want explained this way? Just hit reply — that's exactly what this newsletter is for.

How was today’s email?

Awesome  |   Decent    |  Not Great

Keep Reading