Summary

Steve Yegge describes his workflow as a 'vibe maintainer' of two popular open-source projects (Beads and Gas Town), where he processes ~50 AI-generated pull requests per day using AI agents to help triage and fix them. He argues that refusing AI-generated PRs is a losing strategy because users will simply fork your project, and that the future of OSS maintenance is about maximizing community throughput. His approach inverts conventional wisdom: instead of requesting changes (the traditional first resort), he fixes contributors' code himself, cherry-picks good parts, and reimplements ideas — making rejection the last resort. He details a sophisticated PR triage system with categories ranging from easy-wins to fix-merge to rejection, and explains why 'taste' still requires human judgment for the hardest 5-10% of PRs.

Key Insight

The future of open-source maintenance requires embracing AI-generated contributions rather than fighting them, because in a world where anyone can fork and maintain software with coding agents, community throughput and responsiveness matter more than gatekeeping.

Spicy Quotes (click to share)

• 7

  Now that everyone on earth has access to powerful coding agents, we will see way more forks. Forking used to be a declaration of war. Now it's simply a declaration that someone liked your software enough to want to change it, but you said No.

• 7

  Any grandma who wants to use your software for gardening could build a massive grandma subcommunity with your stuff if you don't take her PRs. She might not even know she's done it.

• 4

  If there is good in the PR, then you should absorb that good into your code base, right there and then, rejecting anything you don't like, and transforming the parts you're absorbing.

• 8

  And you say, Claude, it's a fucking face-hugging alien. And Claude says, oh right, that's a very good point, we probably don't want that, shall I close it with a polite note?

• 6

  And that's why the last 25% or so of pull requests need human review. At least, so far. It's because there's still a thing called taste that current models can't be trusted with.

• 5

  Software survival is now about velocity — specifically, keeping up with what your users want.

• 7

  The whole status quo in open-source is characterized by historic levels of silliness.

• 4

  I'm a very lazy person, and maintaining a popular OSS repo, let alone two of them, would simply not have been possible for me, like ever, up until maybe a year ago.

Tone

opinionated, conversational, pragmatic