March 22, 2026
Summon bots, embrace chaos
How to Attract AI Bots to Your Open Source Project
Satirical ‘lure the bots’ guide has devs cackling, cringing, and plotting chaos
TLDR: A jokey guide suggests attracting AI code bots by making messy, welcoming projects—and people lost it. Commenters laughed at the satire, debated “free compute” ethics, and recoiled at cursed tips like committing giant dependency folders, turning a gag into a real conversation about AI’s messy role in open-source.
A developer jokingly wished for more AI-made pull requests (PRs—suggested code changes) and instantly got one written by Claude, merged as his first AI-assisted contribution. Then came a tongue‑in‑cheek “playbook” on how to attract robot contributors: write vague issues, post a bots welcome guide, keep a huge backlog, turn off safeguards, and even ditch tests and type checks. The punchline: maybe even commit your massive “node_modules” folder (a giant pile of app add‑ons) to give bots more files to nitpick.
The crowd went feral. Some admit they were fooled at first, then the humor hit like a freight train. One reader clocked the absurdity when it escalated to “disable branch protection” (the safety rules that keep bad changes out) and “include node_modules.” Another deadpanned they weren’t sure what layer of irony they’d fallen into, but committing that folder is awful in any universe. The spiciest take? A commenter called it “harvesting free computation,” wondering if people are basically turning wandering AI agents into unpaid interns.
Jokes flew—someone proposed a cursed GitHub badge for bot-bait repos, others imagined a porch light labeled “good first issue” to summon typo-fixing automatons. The split: half see brilliant satire skewering today’s AI hype, half fear it’ll inspire chaos PRs that break more than they fix. Either way, the bots are listening—and the comments are screaming.
Key Points
- •An open-source maintainer reports receiving no AI-authored PRs despite active, starred repositories.
- •A collaborator used Claude to write the post and submitted it via pull request, which was merged.
- •The author claims a median of 4.7 AI-authored PRs per month for repositories with over 500 stars.
- •Recommended tactics include writing vague issues and welcoming automated contributions in CONTRIBUTING.md (or AI_CONTRIBUTING.md).
- •Further suggestions are maintaining a large backlog, disabling branch protection, and removing types/tests to increase bot engagement.