Computing Life · Share · YageAug 16, 2026, 08:00 UTC+8

A cron job and acceptance criteria can keep a codebase maintained

Boris Cherny's team ran a daily Claude routine that opened 388 PRs over several weeks, with 180 merged into main. The key isn't model smarts—it's the trigger, acceptance criteria, and review funnel working together. Cherny moved the trigger out of chat windows and into a cron job; when output missed the mark, they adjusted the routine definition instead of patching code. The post doesn't disclose whether the 208 unmerged PRs were rejected, duplicated, expired, or queued. A 46.4% merge rate shows candidate submissions naturally outpace actual merges—the review funnel is part of the design.

Why it matters: Boris Cherny moved Claude's trigger from the chat window to a cron job — 180 of 388 PRs merged. The story isn't model smarts, it's the trigger-acceptance-review funnel working together. Not scoring 85+ because the post doesn't disclose why the other 208 PRs failed or the total...

Read the original ↗Export Markdown

Take

This one's worth opening because Boris Cherny moved Claude's trigger out of a chat window and into a daily cron routine. Over several weeks, it opened 388 PRs—180 merged, a 46.4% merge rate that shows candidate submissions naturally outpace actual merges. The review funnel is part of the design, not an afterthought.

I'd discount it a bit: the post doesn't say whether the 208 unmerged PRs were rejected, duplicated, expired, or queued, and total agent runs aren't disclosed. But the core idea is solid—define what "done" looks like and how to verify it, let the agent figure out the middle, and have engineers guard only the final gate. Dead code cleanup ran in two beats: day one inserts logging, day two checks the data and proposes deletion. No need to pre-code every decision branch.

What's copyable isn't Anthropic's internal architecture—it's the mounting pattern. Pick a grunt task that's hard to script but has clear acceptance criteria, attach a cron or event trigger, and grant PR-suggestion rights only, never merge access or production credentials. When output misses, fix the routine definition that runs tomorrow, not the code with one-off patches.

Source: Computing Life · Share · Yage · yage.ai
Published: Aug 16, 2026, 08:00 UTC+8 · Aug 16, 2026