← In the News

Searls hands his backlog to agents and keeps only the decisions

I'm just a meat proxy · Justin Searls, co-founder of Test Double · justin.searls.co, November 11, 2026

Machine-readable Download Markdown

Searls writes: "My agents are currently shipping 20 to 40 issues a day across the dozen or so iOS apps I'm building." Every app has a reporting button that files a GitHub issue with the last minute of screen recording and his spoken narration, logs, and a deep link to the screen he was on. Scheduled jobs on two Macs give each issue a fresh agent; bugs are reproduced first and ship with before and after recordings, and a physical iPhone and iPad stay attached for agents to test on. In his account, "6 to 10 issues get a human label slapped on them" each day because an agent is stuck, and those become cards in an app he calls MeatProxy. A daily retro agent reads the previous 24 hours and proposes changes; he says one retro found and repaired the watchdog that should have killed a set of stuck agents.

He does not release the app. He posts a long build spec instead, and it is specific about where autonomy stops. "Code decides, models work": scheduling, eligibility, retries and budget gates are plain scripts. Review comes from "a fresh session that did not write the code, ideally a different model, never a self-review." Two unfinished attempts at an issue send it to a human. On permissions he is blunt: headless agents run with prompts bypassed, and "Bypass is what makes the loop work and it means an issue's text can run commands," so the spec pairs that with a trusted-author rule, a scoped bot account and a Mac holding no production credentials. The throughput figures are his own and unaudited, and he concedes he is "almost certainly accumulating a mountain of technical debt."

Why it matters: This is a working single-developer factory with its control points written down: what a script decides, what a model does, when a human is pulled in, and the security cost of running unattended. The spec is directly reusable as a checklist even if you never build the phone app.