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 two hundred 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

Phil SchmidVoices

Why Agents Are Soon Only Going to Have 1 Tool

11.01

Instead of triggering tools one at a time across turns, agents are collapsing their tool catalog into a single exec(code) tool—chaining, filtering, and awaiting actions inside an isolated sandbox.

Agents & vibe coding

Read at Phil Schmid ↗

One letter a week, starting soon.

Latest

Why Agents Are Soon Only Going to Have 1 Tool

Related

VoicesCredentials API for Gemini Managed Agents Phil Schmid

VoicesEvaluating Agents Beyond the First Prompt Phil Schmid

VoicesBuilding Managed Agents That Use GitHub Without Exposing Your Token Phil Schmid

VoicesControl an Android Phone with Gemini 3.5 Flash Computer Use Phil Schmid

VoicesHow Gemini Managed Agents Works under the Hood Phil Schmid

VoicesGemini Managed Agents: Developer Guide Phil Schmid