Sources: posts I reposted on X between September and October 2026: Josh Rosen’s Software Factories for Skeptics (via Matt Stockton), Josh Rosen’s The Software Factory Debate: Build, Buy, Fork or Delegate, Lauren’s (@poteto) 2,500 PRs talk and Matt Pocock’s notes on it, and Tailscale on the Secure Software Factory.

“Software factory” kept showing up in my feed this month. My first reaction was the same as most people’s: that sounds like a lights-out shop where nobody reads the code. After reading the posts I reposted side by side, I think that framing is wrong, and the useful version is much smaller and much closer to what I already do.

This post pulls the threads together. In Background Agents: What 13 Companies Actually Run I looked at the runtime. This one is about the system around it.

Read More

Sources: Background Agents Summit session pages and the YouTube talks (6-7 May 2026). Definition from background-agents.com. I used Ona’s summit recap and llms-full.txt as indexes. Where a talk, a session page, and other Ona pages disagree, I leave the disagreement in.

I have been treating coding agents as a laptop problem: more terminals, more worktrees, more parallel sessions. That is useful. It is also the wrong unit of scale.

The Background Agents Summit put a sharper name on the next layer. Thirteen talks, recorded 6-7 May 2026, from Stripe, Uber, Cloudflare, Harvey, Open Inspect, Genentech, incident.io, Monzo, AWS, Tessl, Ona, Nono, and software-factory.dev. The claim is not that agents write more code. The claim is that org cycle time stays flat until the work leaves the laptop.

I am reading this as a field review. The useful part is how independently these teams landed on the same runtime.

Read More