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

GitHub ChangelogGitHub

Unvalidated npm trusted publishing configurations now expire

October 2

Unvalidated npm trusted publishing configurations now expire 48 hours after creation and can no longer authorize publishing.

Read at GitHub Changelog ↗

One letter a week, in your inbox.

Latest

Unvalidated npm trusted publishing configurations now expire

More from GitHub Changelog on Accept All

GitHubnpm staged publishing now supports creating new packages GitHub Changelog

GitHubSelected models in GitHub Copilot deprecated GitHub Changelog

GitHubNew fields for SecurityAdvisory GraphQL API GitHub Changelog

GitHubConfidential comments on repository security advisories GitHub Changelog

GitHubRate limits for private vulnerability reports GitHub Changelog