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

Vercel BlogTools

Introducing Vercel Drives: persistent storage for agents

10.15

Agents often handle complex work that continues across runs. As that work evolves, they may need a new environment with different tools, runtimes, or compute.

Agents & vibe coding

Read at Vercel Blog ↗

One letter a week, starting soon.

Latest

Introducing Vercel Drives: persistent storage for agents

Related

JapanClaude Codeデスクトップアプリ、並行作業を進めやすくするセッション管理の改善を案内 gihyo.jp

GitHubUnblock agentic software delivery with governed code review GitLab Blog

ToolsAI Agent Security Risks: What Can Go Wrong When Agents Act on Their Own Docker Blog

ToolsHarbor + Docker Sandboxes: Run Safe, Reproducible Agent Evals Docker Blog

VoicesCrossing the Threshold: How OpenAI and Anthropic Approach Autonomy and Safety in Financial Agents Latent Space

ValleyEpic says its new vibe-coded Epic Games Launcher is faster than Steam Ars Technica AI