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

The New StackGitHub

The context problem: How Docusign built agents that understand the business behind contracts

10.31

Ask a general-purpose language model to summarize a contract, and it will probably do a reasonable job.

Agents & vibe coding

Read at The New Stack ↗

One letter a week, starting soon.

Latest

The context problem: How Docusign built agents that understand the business behind contracts

Related

GitHubAWS’s Hydro team wants the compiler to catch coding agents’ mistakes The New Stack

GitHubMicrosoft’s new Copilot harness makes agents easy — until you want to switch The New Stack

GitHubWhy MCP servers should tell agents what to do next The New Stack

GitHubThe 5 essential layers of AI agent sandboxing on Kubernetes The New Stack

GitHubGoogle just handed its rivals the keys to Android The New Stack

VoicesAgents Prompt People: Using Agents for Long-Horizon Financial Work Latent Space