Work through a flood of GitHub issues after an open-source launch

A solo developer used Claude Code to investigate and fix bug reports on holyarrs, his self-hosted media app, closing 309 GitHub issues and shipping 26 releases in 8 days.

Done withClaude CodeinGitHub· Nov 18, 2026

What they did

Reddit user u/CoderLuii had just launched holyarrs, a free, open-source app that replaces the half-dozen tools a home media server usually needs. The launch drew far more users than he expected, and bug reports and feature ideas arrived faster than he could read them. He set up a daily loop: start the day with the new GitHub issues, pick one, hand it to Claude Code to investigate and fix, test the result himself on a real media server, ship a release, answer the person who filed it, then take the next one. On busy days that loop ran five or six times. In the same stretch he also added an MCP server, 4K requests with owner approval, and the app in 44 languages.

How it went

Eight days after launch he reported 309 closed issues and 26 releases, along with 1,445 GitHub stars and about 23,800 Docker pulls. Some users sent their own fixes, which he credits as part of the pace. He says he was working more than 16 hours a day to keep up, so the agent sped up the fixing but did not take him out of the loop. The app is still labelled beta.

Worth knowing

Every fix was checked by hand on a real setup before it shipped; the agent did the digging, not the testing. The post gives no split of how many issues Claude Code fixed versus contributors. One commenter suspected Claude wrote the post itself, and another warned the project site used copyrighted poster images that could draw takedown notices.

Try it

With Claude Code· 2 parts to fill in

Open the newest unhandled issue in [my GitHub repo]. Read it and any linked logs, reproduce the problem locally if you can, find the cause in the code, and write the smallest fix with a test that fails before it and passes after. Then give me short steps to check the fix on [my real setup, e.g. my home server]. Draft a reply to the person who filed the issue, but do not post it, push, or cut a release until I have tested it and said go. Then move to the next issue.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related