A weekday email for software engineers working alongside AI agents. Five minutes: what changed, whether it matters for you, and one thing to try.

Sample.

A stale test command cost agents a third more calls

  1. 001When Instruction Files Go Stale found stale commands cost agents extra calls
  2. 002Apiiro found Claude Code approvals leaking passwords into 1,122 public files
  3. 003AgentBaton cut API costs 65.9% by handing work to cheaper models
  4. 004Simon Willison hides agent-written PR descriptions behind a human summary
  5. 005Claude Code v2.1.319 changes auto mode behind LLM gateways

How.

  1. 001Every weekday, a pipeline reads 57 sources: 53 feeds, Hacker News, Hugging Face daily papers, Lobsters and new GitHub repos.
  2. 002Today, 155 items became 14 shortlisted, then 5 bullets you can skim.
  3. 003Each story gets TRY, WATCH or SKIP. The one thing leads; Safe to ignore names the hype.

Who.

Written by John Young, a CTO who runs coding agents in production.

He builds flywheel, an open-source agent orchestrator.

Join.

Agentic AI, evaluated every weekday. Five minutes.

2026-11-09.md

Monday 9 November 2026

A stale test command cost agents a third more calls

Five bullets

The one thing

Stale instruction files quietly tax every agent session

When Instruction Files Go Stale measured what outdated AGENTS.md and CLAUDE.md files cost coding agents. With a stale test command, Claude Sonnet 5.5 needed about two extra tool calls per run. That is a third more than with the corrected command. For the other two stale instructions, the authors could not detect a difference.

The study took three real stale instructions from active open-source repos. One was a test command, one a code location, and one a procedure for adding a component. Agents fixed 22 maintenance tasks with each instruction left stale, corrected or removed. The authors analyzed 732 trajectories from two models, one tool call at a time.

Agents followed stale guidance when it was relevant to the task. Sometimes they followed it even when correct information existed elsewhere. They usually recovered, so the task still passed. None of them repaired the instruction file.

Correcting the file eliminated operations on obsolete paths. Removing the stale line prevented most of them. The skill that grows is keeping your instruction files true, because your agent will not.

Check the paths and commands in your instruction files, because your agent will not fix them.

Try this · 15 minutes

Find the stale lines in your agent's instruction file

  1. Open the AGENTS.md or CLAUDE.md in a repo you work in every day.
  2. List every test command, file path and procedure it tells the agent to follow.
  3. Run each command and check that each path exists in the current repo layout.
  4. Correct each stale line, or remove it if you cannot fix it now.

Stories

Safe to ignore

57 sources read. 155 items. 14 shortlisted. 5 bullets.