I'm tired of the quarterly "bug bash" ritual where we just

远程办公技术宅 Intermediate 53m ago 578 views 14 likes 2 min read

We’ve all been there. You open your error tracker, see 500 "High Priority" issues, realize none of them actually impact real users, and eventually just mass-select everything and mark it as resolved because the backlog is a graveyard. It's a waste of engineering time. The problem is that modern error tracking is broken: it's either drowning you in false positives (thousands of errors that don't matter) or missing the silent killers—the false negatives where nothing throws an exception, but the user experience is a total disaster.

I've been looking into Opslane, an open-source LLM agent designed to actually close that loop. Instead of just being another dashboard you ignore, it acts like a junior dev that watches user sessions and investigates why things are breaking.

How it actually handles the "silent killer" bugs

The most interesting part isn't just the error catching; it's how it tackles those bugs that don't trigger a single exception. If a user clicks a dropdown and it immediately closes, your server logs look perfect. Sentry sees nothing. But Opslane looks at session recordings to spot "rage clicks," dead clicks, or users abandoning a form halfway through.

It recently caught a bug in a customer's onboarding flow where a dropdown was behaving erratically. No error log was generated, but the session recording showed users clicking, getting nothing, and leaving. The agent flagged the pattern, and the team actually fixed it.

The AI workflow: Moving from dashboard to Claude Code

If you are deep into the current wave of AI coding tools, you know the goal is to stay in your IDE. Opslane is leaning heavily into this by shipping an MCP (Model Context Protocol) server. This is huge for anyone using Claude Code or similar tools.

Instead of jumping into a web UI to find out what went wrong, you can literally ask your terminal:

# Hypothetical interaction via Claude Code with Opslane MCP
claude > "What broke for users this week?"

The agent pulls the relevant context, identifies the high-impact issues, and because it's "product-aware" (it reads your codebase and watches the recordings), it can actually propose a fix. It only creates a PR if it can verify the fix, which is the only way I'd trust an autonomous agent in my repo.

Deployment and setup

Since it's open-source, you aren't locked into a massive SaaS subscription just to see your logs. You can spin it up locally or on your own infra using a single Docker Compose file.

To get the data flowing, you just drop in the SDK. It captures:

Console logs
Network requests
Full session recordings
Error stack traces

It then ranks these based on actual user impact rather than just arbitrary severity levels. It's basically trying to build what an error tracker would look like if it were designed in 2026, rather than 2016.

If you're sick of staring at Sentry backlogs that never get touched, this is definitely worth a look for your deployment pipeline.