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

Vercel BlogTools

Vercel CI no longer requires a linked Vercel project

11.03

Vercel CI can now run on a GitHub repository that has no Vercel project. Until now you had to create an empty project just to connect the repository.

Read at Vercel Blog ↗

One letter a week, starting soon.

Latest

Vercel CI no longer requires a linked Vercel project

More from Vercel Blog on Accept All

ToolsHow Zapier turns ideas into working software in hours with Vercel Vercel Blog

ToolsHow Mercor ships internal apps and billions of production tokens on one platform Vercel Blog

ToolsVercel MCP now supports Client ID Metadata Documents Vercel Blog

ToolsVercel MCP now renders deployments as an interactive card Vercel Blog

ToolsIntroducing Vercel Security Review Vercel Blog

ToolsLongCat 2.5 now available on AI Gateway Vercel Blog