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

LangChainTools

How We Made Our Docs Test Themselves

10.13

Stale code samples are a docs problem nobody prioritizes. Here's how we used the Deep Agents CLI to automate migrating inline code into testable, CI-ready…

Read at LangChain ↗

One letter a week, starting soon.

Latest

How We Made Our Docs Test Themselves

More from LangChain on Accept All

ToolsHow Orange Business Built Live Intelligence with LangChain and LangSmith LangChain

ToolsMCP in LangChain: Stateless Protocol, Elicitation, and More! LangChain

ToolsDeep Agents Deploy: an open alternative to Claude Managed Agents LangChain

ToolsOpen Models have crossed a threshold LangChain

ToolsContext Management for Deep Agents LangChain

ToolsImproving Deep Agents with harness engineering LangChain