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

LobstersGitHub

An open format for writing agent-native software requirements

10.29

Comments

Agents & vibe coding release practices building-ai-tooling

Read at Lobsters ↗

One letter a week, starting soon.

Latest

An open format for writing agent-native software requirements

Related

LabsAccelerate agentic AI with NVIDIA Nemotron models on Amazon EKS and SageMaker HyperPod EKS AWS Machine Learning

SiliconHow Vision and Connectivity Enable Autonomous Agriculture EE Times

SiliconBuild, test and optimize faster: Arm and GitHub accelerate agentic AI development Arm Newsroom

SiliconInto the Omniverse: How Developers Turn Ideas Into Simulations With Frontier AI Agents NVIDIA Blog

GitHubWhy MCP servers should tell agents what to do next The New Stack

GitHubBug0 Releases QA Agent to Automate Regression Testing With Cached Playwright Replays InfoQ AI