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

AI Governance: One view of agent activity

10.20

AI coding agents are writing and changing code, from GitLab Duo Agent Platform agents to externally connected agents like Claude Code, Cursor, and Codex.

Agents & vibe coding

Read at GitLab Blog ↗

One letter a week, starting soon.

Latest

AI Governance: One view of agent activity

Related

GitHubRedesign how your team ships software with AI agents GitLab Blog

GitHubThree developer tasks worth handing to an agent GitLab Blog

GitHubConnect your agents to your software lifecycle with the GitLab MCP server GitLab Blog

GitHubUnblock agentic software delivery with governed code review GitLab Blog

GitHubGemini 4 Argon on GitLab: Built for long-running agentic work GitLab Blog

GitHubScaling Git for the agentic software factory GitLab Blog