I built BugHarbor to connect user feedback to code fixes—looking for first testers
Hey everyone, I’m Fabian, a developer from Suriname 👋
When someone reports “the save button isn’t working,” there’s still a lot of work between that message and a fix: understanding the issue, finding the relevant code, and deciding what to change.
That’s why I’m building BugHarbor.
It brings user feedback and JavaScript errors into one inbox. BugHarbor Agent can investigate reported issues in your repository and prepare a pull request for you to review. You can also send issues to Cursor, Codex, or Claude Code.
I use BugHarbor daily and have been improving the workflows through my own experience. Now I’m looking for our first external users—especially indie developers and small SaaS teams—to see how it works in other projects.
If you’re maintaining a live web app, I’d appreciate you trying it and sharing what feels useful, confusing, or missing.
What usually takes the most effort after a user reports a bug: reproducing it, finding the cause, or preparing the fix?
Replies