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 Next PlatformSilicon

How to Evaluate CPU Performance for Agentic AI

10.29

A funny thing happened on the way from machine learning to chatbots to agentic AI: the central proce ...

Agents & vibe coding Research

Read at The Next Platform ↗

One letter a week, starting soon.

Latest

How to Evaluate CPU Performance for Agentic AI

Related

ToolsReplit’s Architecture Behind Secure Agent Work Replit Blog

LabsBuild agentic retrieval on a Managed Amazon Bedrock Knowledge Base with CDK AWS Machine Learning

ToolsContext Engineering (Agent Memory) for AI Agents Starts with Retrieval LangChain

SiliconHow NVIDIA OpenShell Reference Architecture Secures and Governs AI Agent Workloads at Scale NVIDIA Technical Blog

VoicesNew paper: Emerging trends in AI agent evaluation AI Snake Oil

ToolsHow Legora runs 2,000 parallel agent evals on Modal Sandboxes Modal