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

GitLab BlogGitHub

Pillow CVE-2026-112900: How to find and fix it with GitLab

10.26

GitLab is not affected by CVE-2026-112900 or the other vulnerabilities fixed in Pillow 13.0.0. GitLab products do not include the Pillow library, and our Security team has found no evidence of impact…

Read at GitLab Blog ↗

One letter a week, starting soon.

Latest

Pillow CVE-2026-112900: How to find and fix it with GitLab

More from GitLab Blog on Accept All

GitHubPHP2Shell: GitLab helps find and remediate critical PHP flaws GitLab Blog

GitHubRedesign how your team ships software with AI agents GitLab Blog

GitHubUncover the business logic vulnerabilities SAST scanners miss GitLab Blog

GitHubAI Governance: One view of agent activity GitLab Blog

GitHubThree developer tasks worth handing to an agent GitLab Blog

GitHubBuilding AI security in the open GitLab Blog