Sentry announced new capabilities for Seer, its AI-powered debugging agent, extending debugging support to local development and code review, and introducing a simplified, flat pricing model with unlimited usage.
“Wherever code breaks, Seer helps you fix it faster,” said Sentry CEO Milin Desai. “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. That runtime context allows Seer to diagnose failures that cannot be reliably identified through static code analysis alone, particularly in distributed systems where issues often 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 said. “With that context, we can move beyond flagging issues after the fact to explaining them in real time, automatically identifying the root cause for developers and their coding agents, and even anticipating problems before code goes live.”
Seer combines source code with live application behavior to identify these problems, including:
- Failures that propagate across services or network boundaries
- Latency spikes caused by contention or resource saturation
- Errors that occur only under production traffic patterns
By analyzing how software actually behaves, Seer focuses on determining why a failure occurred, not just where it surfaced.
“Failures in modern systems often cannot be debugged by simply reading the code,” Indragie Karunaratne, director of engineering at Sentry said. “Seer is designed for that reality. It looks at how services behave together at runtime, which makes it possible to identify root causes that static analysis and code review alone can’t catch.”
With this release, Sentry is expanding Seer’s role beyond production debugging to support developers earlier in their workflow.
Seer connects to local coding agents through the Sentry MCP server. As developers reproduce bugs locally, application telemetry is sent to Sentry, where Seer can analyze raw events and perform root cause analysis. That context can be used by coding agents to generate fixes before code is committed.
Seer can analyze pull requests to identify defects likely to cause production failures. The system is designed to focus on high-impact issues rather than stylistic feedback, helping teams catch real bugs before code is merged.
When bugs reach production, Seer automatically identifies the most actionable issues and performs root cause analysis in the background. When sufficient context exists, it can generate suggested code changes or delegate fixes to supported coding agents.
Sentry is also developing an experimental capability that allows developers to ask Seer open-ended questions about their telemetry. This feature is intended for investigations that begin with symptoms rather than a clearly identified bug, such as unexplained performance regressions or anomalous trends. The capability 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, and as a platform teams use to see, explain, and fix what matters,” Desai said.
The Latest
Two years ago, almost every customer conversation about AI started with the same questions: Which model should we use? What can it do? Is it ready for the enterprise? Today, those discussions have moved on. CIOs are far more interested in how to govern AI, integrate it with existing systems, prepare their workforce and make it part of everyday operations. The challenge is no longer to prove that AI can deliver value. It's instead about how to embed AI into the business in a way that's secure, scalable and delivers measurable outcomes ...
Two things happened to production incidents between 2023 and now, and they did not happen at the same speed. The first is that a class of dependency that barely existed three years ago now accounts for one incident in ten. Incidents disclosed by AI model and AI application providers rose from 1.7% of all disclosed unplanned incidents in 2023 to 10.7% in 2026 year to date, roughly a sixfold rise; that counts only incidents at AI companies themselves, so the true share is higher. The second is that the time to close an incident has not come down ...
When an AI assistant gives an incomplete or incorrect answer, teams often blame the model. They adjust prompts, switch models, increase context windows or test a new retrieval strategy. However the model may not be a problem. In many enterprise AI workflows, the problem begins inside the document-ingestion pipeline ...
If you talk to any security or observability teams right now, they're all fighting the same fire: their tooling was built to ingest X, but their sources are pumping Y and soon to be doing Z. The knee-jerk reaction is always the same: we need more platform. However, this reaction is wrong. Let me explain why, because the solution to this problem is foundational, not financial. Instead of hurling yet more money at the problem, make sure you've done what's needed upstream ...
Rapid AI adoption and the unique ways AI workloads operate is redefining the scope and structure of what these teams must deliver. This shift is forcing organizations to rethink how they manage scale, automation, and control, according to The State of SRE and Platform Engineering 2026, a new report from Dynatrace ...
AI is usually talked about as a software tool, but it also depends heavily on the network behind it. Whether a company is using AI for chatbots, automation, monitoring, analytics, or employee support, all of that information has to move across the network in a reliable and secure way. That means AI is not just an application decision. It is also an infrastructure decision. Before organizations rush into AI, they should ask a simple question: Is our network ready to support it? ...
Enterprise AI often lacks governed access to where business processes actually execute. Without that access, AI agents may be able to reason, but they cannot operate reliably across enterprise workflows. For AI agents to effectively carry out workflows, they will require integration-layer context and controls. Organizations can implement these prerequisites by providing AI with managed access to the middleware layer ...
Enterprise networks rarely behave the same way for very long. A routing adjustment in one region may unexpectedly alter application performance in another. A cloud migration may introduce hidden dependencies that go unnoticed until an outage occurs. All the while, the network is managed by several different teams, each of whom use different tool sets — and as a result, have different views of the network ... There’s usually an engineer who remembers why traffic fails over a certain way between sites, or which transparent firewall was added where. The problem is that human memory cannot scale alongside enterprise-scale networks ...
Ask an infrastructure team how confident they are in their ability to govern AI, and most will tell you they've got it handled. A recent survey of 406 IT decision-makers and platform engineering leaders found 86% expressing exactly that confidence. Ask the same group whether they have a formal written AI governance policy, and the number drops to 30%, according to Spacelift's Infrastructure Automation Report ...
In MEAN TIME TO INSIGHT Episode 27, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and Parker Hathcock, EMA Research Director covering IT Service/Operations (ServiceOps), discuss observability unification in modern IT operations ...