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

Most AI incident tools still leave a key decision to humans

October 8

An AI SRE agent can help troubleshoot an incident. But can you trust it to decide on its own when something needs attention?

Read at The New Stack ↗

One letter a week, in your inbox.

Latest

Most AI incident tools still leave a key decision to humans

More from The New Stack on Accept All

GitHubYour AI agent just provisioned a resource. Who owns it? The New Stack

GitHubThe audit log says my name: what an agent inherits when you hand it your credentials The New Stack

GitHubAI data lakes are driving new storage demands The New Stack

GitHubThe API tax: Why AI agents stall without infrastructure context The New Stack

GitHubAI changed how you respond to incidents. Your tabletops haven’t caught up. The New Stack

GitHubClaude Sonnet 5.5 vs. Opus 5.5: 42% cheaper and perfect on every run The New Stack