Radar

Week 4 · Nov 2 to 8, 2026

Unlearn Radar Week 4

We're getting pretty good at making coding agents do things. The harder question is whether the things we're doing actually make them better. Next.js is now publishing agent evals that measure success, cost and time, even comparing results with and without AGENTS.md. This week, Why AI Needs Evals, Not Vibes looks at why measuring agents matters, while Build an Eval for Your Coding Agent puts it into practice.

We're also questioning what we give agents in the first place. The Agent Doesn't Need to Know Everything looks at giving agents the right information when they need it, and Measure Whether AGENTS.md Actually Helps tests whether those extra instructions really improve results. You can go further with planning and context in our Product Engineer role.

Finally, as coding tools give us more choice over which models do the work, One Model vs Model Routing tests whether choosing the right model for each task can beat sending everything to one capable model.

Alex Garrett-SmithNov 3

This week's Versus

Should your AI code reviewer pick a model for each pull request, or send every pull request to the same one?Model RoutingRules on the diff send small changes to a cheaper, faster model and risky ones to the best.Single ModelEvery pull request goes to the same model with the same prompt, whatever its size.Routing PR reviews by size and risk saves money and waiting on small changes; I'd start with one model and route once the bill or the wait matters.Read the comparison

What Radar publishes

Weekly noteEvery week
VersusEvery few weeks
TLDRsSeveral a week
This Week in AI DevComing soon
The Unlearn PodcastComing soon