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

Sourcegraph BlogTools

How to evaluate Sourcegraph on your own codebase

07.31

Better code retrieval does not automatically mean better task completion. Here is how to measure retrieval, agent performance, and cost without confusing one for another.

Research

Read at Sourcegraph Blog ↗

One letter a week, starting soon.

Latest

How to evaluate Sourcegraph on your own codebase

Related

ToolsAutoscaling endpoints for LLM inference Together AI

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

VoicesAn OpenAI model hacked Hugging Face to help it cheat on a benchmark Understanding AI

ToolsGoogle’s Gemini 3.6 Flash and 3.5 Flash-Lite Benchmark Scores Weights & Biases

VoicesLWiAI Podcast #252 - GPT 5.6, Grok 4.5, Nemotron-Labs-Diffusion, AI 2040 Last Week in AI

VoicesControlling Reasoning Effort in LLMs Ahead of AI