Sentry has announced new capabilities for Seer, its AI-powered debugging agent, extending support to local development and code review while introducing a simplified flat pricing model with unlimited usage.

“Wherever code breaks, Seer helps you fix it faster,” said Milin Desai, CEO of Sentry. “It’s the next step in Sentry’s evolution; a fundamentally smarter way to understand what’s happening with your code from development to production, and how to fix it.”

Seer is built on Sentry’s production telemetry, including errors, traces, logs, and metrics. This runtime context allows Seer to diagnose failures that static code analysis alone often misses—especially in distributed systems where problems cross service and infrastructure boundaries.

“After more than a decade of helping developers find and tackle bugs, Sentry has an unrivaled understanding of what breaks in production and why,” Desai added. “With that context, we can move beyond flagging issues after the fact to explaining them in real time, automatically identifying root causes, and even anticipating problems before code goes live.”

Debugging Grounded in Runtime Behavior

While AI coding tools can detect some issues by analyzing source code, many real-world failures only appear at runtime. Performance regressions, cascading failures, and load-related issues often depend on conditions invisible in static code.

Seer combines source code with live application behavior to identify issues such as:

• Failures that propagate across services or network boundaries
• Latency spikes caused by contention or resource saturation
• Errors that occur only under real production traffic patterns

By analyzing how applications actually behave, Seer focuses on understanding why a failure occurred, not just where it surfaced.

“Failures in modern systems often cannot be debugged by simply reading the code,” said Indragie Karunaratne, Director of Engineering at Sentry. “Seer looks at how services behave together at runtime, which makes it possible to identify root causes that static analysis alone can’t catch.”

Shifting Left Across the Development Lifecycle

With this release, Sentry is expanding Seer’s role beyond production debugging to support developers earlier in their workflows.

Local Development

Seer connects to local coding agents through the Sentry MCP server. As developers reproduce bugs locally, telemetry is sent to Sentry, allowing Seer to perform root cause analysis and help generate fixes before code is committed.

Code Review

Seer can analyze pull requests to identify defects likely to cause production failures. Rather than focusing on style, it prioritizes high-impact issues, helping teams catch real bugs before merging code.

Production

When issues reach production, Seer automatically identifies the most actionable problems and performs background root cause analysis. Where sufficient context exists, it can suggest code changes or delegate fixes to supported coding agents.

Investigating the Unknown

Sentry is also developing an experimental capability that allows developers to ask Seer open-ended questions about their telemetry. This feature is designed for investigations that start with symptoms—such as unexplained performance regressions—rather than a clearly identified bug. It is currently available in early preview for select customers.

“Seer represents our broader vision: Sentry as the intelligence and reasoning layer for modern software development,” said Desai. “A platform teams use to see, explain, and fix what matters.”

Pricing and Availability

Alongside the general availability of Seer, Sentry introduced a simplified pricing model:

• $40 per active contributor per month
• Unlimited usage
• Contributors are counted if they create at least two pull requests in a connected repository during the month

This model eliminates usage limits and complex seat management, making AI-powered debugging more accessible across development teams.