AI agent now supports earlier bug detection under a single flat pricing model<\/p>\n
Sentry today 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.<\/p>\n
\u201cWherever code breaks, Seer helps you fix it faster,\u201d said Sentry CEO Milin Desai. \u201cIt\u2019s the next step in Sentry\u2019s evolution; a fundamentally smarter way to understand what\u2019s happening with your code from development to production, and how to fix it.\u201d<\/p>\n
Seer is built on Sentry\u2019s unique 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.<\/p>\n
\u201cAfter more than a decade of helping developers find and tackle bugs, Sentry has an unrivaled understanding of what breaks in production and why,\u201d Desai said. \u201cWith 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.\u201d<\/p>\n
Debugging grounded in runtime behavior<\/p>\n
AI coding tools can identify some issues by reading source code, but many real-world failures only surface at runtime. Performance regressions, cascading service failures, and load-related issues often depend on conditions that are not visible in code alone.<\/p>\n
Seer combines source code with live application behavior to identify these problems, including:<\/p>\n
Failures that propagate across services or network boundaries<\/p>\n
Latency spikes caused by contention or resource saturation<\/p>\n
Errors that occur only under production traffic patterns<\/p>\n
By analyzing how software actually\u00a0behaves, Seer focuses on determining why a failure occurred, not just where it surfaced.<\/p>\n
\u201cFailures in modern systems often cannot be debugged by simply reading the code,\u201d Indragie Karunaratne, director of engineering at Sentry said. \u201cSeer 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\u2019t catch.\u201d<\/p>\n
Shifting left across development<\/p>\n
With this release, Sentry is expanding Seer\u2019s role beyond production debugging to support developers earlier in their workflow.<\/p>\n
Local development<\/p>\n
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.<\/p>\n
Code review<\/p>\n
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.<\/p>\n
Production<\/p>\n
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.<\/p>\n
Investigating the unknown<\/p>\n
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.<\/p>\n
\u201cSeer 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,\u201d Desai said.<\/p>\n
Pricing and availability<\/p>\n
Alongside the general availability of Seer, Sentry announced a simplified pricing model:<\/p>\n
$40 per active contributor per month<\/p>\n
Unlimited usage<\/p>\n
Contributors are counted if they create at least two pull requests in a connected repository during the month<\/p>\n
The model removes usage limits and seat management.The post Sentry Adds Local Development and Code Review Debugging to Seer first appeared on AI-Tech Park.<\/p>\n","protected":false},"excerpt":{"rendered":"
AI agent now supports earlier bug detection under a single flat pricing model Sentry today 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. \u201cWherever code breaks, Seer helps you fix…<\/p>\n
The post Sentry Adds Local Development and Code Review Debugging to Seer<\/a> first appeared on AI-Tech Park<\/a>.<\/p>\n<\/div>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-container-style":"default","site-container-layout":"default","site-sidebar-layout":"default","disable-article-header":"default","disable-site-header":"default","disable-site-footer":"default","disable-content-area-spacing":"default","footnotes":""},"categories":[4,1],"tags":[3],"class_list":["post-878","post","type-post","status-publish","format-standard","hentry","category-ai","category-ai-and-ml","tag-ai"],"yoast_head":"\n