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

Ahead of AIVoices

Using Local Coding Agents

06.27

Many people reached out to me in the past asking about my local agent stack as well as how I set up my local agent stack.

Agents & vibe coding

Read at Ahead of AI ↗

One letter a week, starting soon.

Latest

Using Local Coding Agents

Related

VoicesComponents of A Coding Agent Ahead of AI

VoicesAIUC-1: Building trust in AI agents Practical AI

JapanLet AI agents debate: Redesigning the development process with multi-agent collaboration LINE Engineering

JapanWith great verification comes great velocity: How agents raised the stakes at Flava API Gateway LINE Engineering

JapanArchitecting Semantic Context OS: Beyond token stuffing in agentic systems LINE Engineering

ToolsClosing the loop: Evaluating and improving Replit Agent at scale Replit Blog