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

Software Engineering DailyVoices

Scaling Agent Workloads at Vercel

09.17

Most AI agent setups today are built around a single session, where one user interacts with one agent at a time.

Agents & vibe coding Research

Read at Software Engineering Daily ↗

One letter a week, starting soon.

Latest

Scaling Agent Workloads at Vercel

Related

ResearchSOP-Bench: A new benchmark for evaluating AI agents on real business procedures Amazon Science

ToolsOpen-sourcing evals for open-weight agents Cline Blog

ResearchA new benchmark for evaluating patient-facing health AI agents Amazon Science

ResearchCapturing token IDs during agentic interactions for better reinforcement learning Amazon Science

LanguagesModular: Modular 26.4: SOTA MoE Serving, Model Bringup via Agent Skills, Mojo 1.0 Beta 2 and More Mojo Blog

ToolsOpus 4.7 for 33% less: How Auggie beats Claude Code on cost and quality Augment Code