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

The New StackGitHub

AWS’s Hydro team wants the compiler to catch coding agents’ mistakes

10.29

Earlier this month, the team behind Hydro developed a new way to check that a distributed system still works correctly when it resends messages after a failure.

Agents & vibe coding Languages & runtimes

Read at The New Stack ↗

One letter a week, starting soon.

Latest

AWS’s Hydro team wants the compiler to catch coding agents’ mistakes

Related

ToolsPrompts That Can Write Themselves: A Kotlin Experiment JetBrains Blog

ToolsLangSmith LLM Gateway: Runtime Controls for Agents LangChain

SiliconInside NVIDIA Sentry: Secure AI Agents at Runtime NVIDIA Technical Blog

ToolsAI Agent Security Risks: What Can Go Wrong When Agents Act on Their Own Docker Blog

ToolsMicrosoft agentically ports Copilot runtime to Rust for $120K DevClass

ToolsMigrating the GitHub Copilot runtime to Rust, using Copilot GitHub Copilot Blog