
Opslane is an open-source error tracker that hands you a fix instead of a dashboard. You add a browser SDK that records errors, console logs, network requests and user sessions, with form inputs hidden by default. An AI agent then looks into the bugs your users actually run into, reproduces them in a sandbox, writes a fix and opens a pull request, but only once it can show the fix works. It never merges anything. You review the PR like any other. Issues are ranked by how many users they affect. It also watches session recordings for problems that never throw an error, like rage clicks, dead buttons and forms people give up on. Every day you get a Slack digest of fixes ready to merge and issues that need a decision. It's MIT-licensed, self-hosts from one Docker Compose file, and for now covers browser JavaScript apps with code on GitHub. This one is for developers.
The founder's story explains the product. At Robinhood, his team held quarterly bug bashes against a Sentry backlog, fixed what they could, then selected everything left and marked it resolved. Any engineer who has declared error-tracker bankruptcy will recognize that. Dashboards help you sort bugs, but users keep hitting them. Opslane's answer is to make a verified pull request the end result, and the rest of the design follows from that.
The safeguards are unusually disciplined. It never merges, so every PR waits for a human. Each run ends in a clear state: a verified fix, an unverified draft you opted into, a written investigation, or an incident that needs a person, with a reason. Inputs are masked before anyone, including the agent, sees a recording. And it all self-hosts from one Docker Compose file, so session data can stay on your own servers.
It only covers browser JavaScript apps with code on GitHub for now. If your team objects to AI-written code because of the review burden, note that reviewing the agent's PRs is the whole workflow. And if your Sentry triage genuinely works, this solves a problem you don't have.
What decides it is how often the fixes really hold, how many PRs are mergeable, and how many false alarms its frustration detection raises on real traffic. The free tier and self-hosting make that cheap to find out. Try it on something small before pointing it at the part of your app that makes money.