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

Docker BlogTools

Where should your code live in a Docker Sandbox?

11.02

Giving an agent a sandbox also means deciding which files it will work on. You can share a checkout from your host, give it a separate working directory for a task, or keep the repository entirely…

Read at Docker Blog ↗

One letter a week, starting soon.

Latest

Where should your code live in a Docker Sandbox?

More from Docker Blog on Accept All

ToolsThe Ecosystem is the Answer: Docker, the Blueprint Alliance, and the Importance of Collaboration in the Agentic Era Docker Blog

ToolsCoding Agent Horror Stories: The CVE That Did Not Exist Docker Blog

ToolsActiveState Partners with Docker to Secure the Open Source in Enterprise Containers Docker Blog

ToolsYour Agent Runs in a Docker Sandbox. Now It Can Join a Team. Docker Blog