Watches user sessions, finds bugs that matter, and fixes them

Hacker News

Share card

Watches user sessions, finds bugs that matter, and fixes them

Hey HN, I’m Abhishek. I'm building Opslane, an open-source agent that identifies user-facing issues and investigates them. It only creates a PR if it can verify the fix. Demo: https://youtu.be/ccuOTYQMeYg Docs: https://docs.opslane.com At my last job at Robinhood, we used to do a quarterly bug bash. We would go through our Sentry backlog and try to fix as many of them as possible. We only fixed bugs we knew were reported by customers. We had hundreds of bugs, and Sentry’s default priority levels made no sense. After the bug bash, we would declare bankruptcy - select all remaining bugs and mark them as resolved. This problem has only gotten worse since coding agents have become more prevalent. So I started thinking: what would Sentry look like if it were built in 2026? To me, error trackers have two failure modes: 1. False positives: They show you thousands of errors, and you can’t tell the impact on the user 2. False negatives: Many user-facing issues don’t throw exceptions, so they go unnoticed. Opslane combines error tracking and session recording. And there is an agent that acts on both. To get started, you install the Opslane SDK. It captures everything the user did: errors, console logs, network requests, and session recordings. Opslane reduces false positives by ranking issues based on how many users are facing a particular issue. It also learns about your product by reading your code and watching your session recordings. False negatives are harder. Opslane reviews session recordings to spot frustration. They look for rage clicks, dead clicks, and abandoned forms. This recently caught a bug in an early customer’s onboarding flow: a dropdown that closed itself when clicked. No exception, no bug report. The recordings showed users clicking it, selecting nothing, and dropping out of onboarding. Opslane flagged it and the team fixed it. Three guiding principles when building Opslane: 1. Open Source: Self-host with one Docker Compose file. 2.Agent-first: I never want to open an error dashboard again. Opslane ships an MCP server, so you can ask "what broke for users this week" from Claude Code. You get back issues that need your attention and you drive the resolution. 3. It knows about your product: Opslane is continuously learning about your product. Every investigation begins with what it knows about your product. It’s early. Frontend apps work end to end today.I am currently focused on improving reliability and accuracy. Here is a link to our repo: https://github.com/opslane/opslane Would love to get feedback from folks on our approach to this problem!