Show HN: Watches user sessions, finds bugs that matter, and fixes them
热度趋势
趋势数据积累中
百分比基于当前可用热度信号，而非评论数或独立用户人数。
官方发布带来GitHub 模型更新信号，适合跟踪能力变化、生态影响和后续落地。
一款新工具现已推出，旨在监控用户会话，从而发现并修复关键错误。开发者可以利用该工具追踪诸如“ReferenceError: demo is defined”之类的错误，并获取时间戳、URL 和用户代理等详细信息。该工具支持开发环境设置和代码库规范，并欢迎用户在问题追踪器上提交错误报告和功能请求。…
Fix bugs that your users run into.
Opslane finds user-facing bugs and investigates them. It only opens a PR if it can verify the fix.
It records every session. That means it sees the errors, and it also sees the bugs that never throw an exception: the button that does nothing, the form people give up on, the dropdown that closes before anyone can pick from it. Each one is ranked by how many users hit it. The ones that matter get investigated. Some of those fixes become PRs. Some need your attention, so you can drive the resolution.
▶ Watch the demo : a production error becomes a verified pull request.
See it work
Read the digest, make the product call, fix it, link the PR. All from the terminal.
The daily Slack digest: what broke, what's ready to merge, what needs a decision. Images show demo data.
Principles
- Agent-first. I never want to open an error dashboard again. Opslane ships an MCP server, so your coding agent pulls the digest, reads the investigation, and fixes the bug from the terminal.
- It learns your product. From your code, and from watching people use it. Better context, better investigations.
- One Docker Compose file. Postgres and MinIO. That's the whole stack.
How it works
Opslane has four parts:
Component What it does
Browser SDK Captures errors and session recordings in the user's browser, with input masking on by default
Ingestion service Receives what the SDK sends, groups errors, ranks them by how many users they hit
Worker Investigates issues, writes and verifies a fix in a sandbox, and opens the pull request
Dashboard Web app for browsing issues, watching replays, and changing project settings
An error travels through those parts like this:
- Capture. The SDK sends errors and session recordings to the ingestion service. Two lines to install.
- Group. Opslane maps minified stack traces back to real file names using your source maps, and groups every occurrence of the same bug into one issue.
- Qualify. Opslane checks how many users hit the bug and how recently, then reads your repo to decide whether it's a real product problem. Only bugs that pass both checks get investigated.
- Investigate. The worker clones your repo and reads the code until it finds the cause.
- Verify. The fix runs in a sandbox with your build and tests. Everything that passed before has to pass again, and a second model reviews the change.