The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around a hundred and forty sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

PydanticTools

Debugging production from your editor with the Logfire MCP server

09.30

The bug report says checkout is failing. Cursor is open on the file you suspect, and Pydantic Logfire is open in another window on the trace that proves you suspect the wrong file.

MCP, skills & tools Pydantic Logfire MCP

Read at Pydantic ↗

One letter a week, starting soon.

Latest

Debugging production from your editor with the Logfire MCP server

Related

ToolsDurable execution in Pydantic AI agents with AWS Lambda Durability Pydantic

VoicesClaude’s new auto eval tool Hamel Husain

LabsGetting the Source Right, Not Just the Fact: Source-Aware Verification for MCP Agents Hugging Face Blog

ToolsGitHub Copilot app for Beginners: How to build custom workflows with canvases GitHub Copilot Blog

LanguagesAG-UI Protocol now has a first-class .NET SDK .NET Blog

EuropeWhat MCP changes about enterprise software DeepL Blog