# Seer: Debug faster at every stage of development

> Seer is the AI debugger that uses Sentry context to flag breaking changes, automatically root cause issues in production, and fix what you missed.

**URL:** https://sentry.io/product/seer/

---

Seer is Sentry's debugging agent. It turns your telemetry into answers and gets you the fix, right where you're already working.

## Features

### New issue at 2am. PR is ready for review.

When a new issue hits, Seer investigates automatically to find what broke and why.

By the time you open your laptop, there's already a pull request waiting.

### Ask Seer anything.

Not everything starts with a Sentry alert. Sometimes you just know something is… off.

Describe what you're seeing in plain language. Seer pulls the relevant signals and answers the questions that don't have an obvious starting point or solution.

### Debug wherever you work.

Seer doesn't just live in Sentry's UI.

Send fixes to Claude, Copilot, or Cursor.

Fix bugs from a Slack alert.

Start an incident investigation in Slack where your whole team can see what's happening.

## Features

- **Ask Seer Anything**: No context-gathering, no copy-pasting stack traces. Just ask Seer Agent what's wrong and get an answer from your actual production data. — [Learn more](https://sentry.io/product/seer/agent/)

- **Errors come with fixes now.**: Seer Autofix reads the stack trace, traces the root cause through your codebase, and drafts a fix — before you've finished reading the alert. — [Learn more](https://sentry.io/product/seer/autofix/)

- **Catch tomorrow's bugs in today's PR.**: Seer reviews your PRs against real production data — the errors, traces, and failure patterns Sentry has already seen from your app. If your change is going to cause problems, Seer tells you without spamming your PR. — [Learn more](https://sentry.io/product/seer/ai-code-review/)

## FAQ

**How much does Seer cost?**

Seer is available to all Sentry users on a paid plan (Team, Business, or Enterprise) at $40 per active contributor, per month.  An active contributor is anyone who commits two or more PRs in a connected repo.

More details are available in the [Seer pricing docs](https://docs.sentry.io/pricing/#seer-pricing).

**How do I enable Seer?**

All Sentry users on a paid plan or trial can use Seer. You will be prompted to enable Seer and generative AI features within the Sentry interface upon attempting to use them for the first time.

**What issues can Seer fix?**

Seer can fix most bugs and performance issues in your application. Seer includes issue scan, which intelligently tries to determine the likelihood that an issue can be fixed with a code change, and enables you to run Seer on those issues. Alternatively, you can configure Seer to run issue fix automatically on issues that it believes it can help you fix.

**What programming languages does Seer support?**

Seer supports all programming languages and frameworks supported by Sentry, including web (frontend and backend), mobile, and desktop. Virtually all modern programming and configuration languages are supported, and then some more.

**How does Seer protect my data?**

Seer respects your privacy and your data, and it comes with robust guarantees:

AI-generated output from your data is shown only to you, not other customers

Your data is not used to train generative AI models without your express consent (off by default)

We process your data only via [trusted subprocessors](https://sentry.io/legal/subprocessors/) that are not allowed to use your data to train their own models

You can [read more](https://docs.sentry.io/product/ai-in-sentry/ai-privacy-and-security/) in our docs.

**Can I disable Seer and generative AI features in Sentry?**

Teams that want to turn off Seer and generative AI features can go to Settings → Organization → General Settings → Enable Generative AI Features and disable the feature toggle.

## Resources

- [Seer: debug with AI at every stage of development](https://blog.sentry.io/seer-debug-with-ai-at-every-stage-of-development/): Seer already accurately root causes and fixes bugs in production. Now we're expanding its capabilities to help you debug during local development and code review.

- [Seer Docs](https://docs.sentry.io/product/ai-in-sentry/seer/): Learn about Seer, Sentry's AI agent, and managing generative AI features.

- [Seer fixes Seer: How Seer pointed us toward a bug and helped fix an outage](https://blog.sentry.io/seer-fixes-seer-debugging-agent/): How Sentry's AI debugging tool Seer helped identify and fix a cascading region blocklist bug that caused an outage in Seer's own EU deployment.

- [Seer Changelog](https://changelog.sentry.io/changelog/?categories=cmaxs61ka001h5lgk9p052rs5): Stay informed with new features and updates for Seer

- [Debug Faster with Sentry MCP and Claude Code](https://sentry.io/cookbook/debug-with-sentry-mcp-claude-code/): Connect Sentry to Claude Code via MCP so your AI agent can pull issues, read traces and logs, and apply fixes without leaving your editor.

- [Fix Production Issues in Cursor with Sentry MCP + Seer](https://sentry.io/cookbook/fix-issues-sentry-mcp-cursor/): Connect the Sentry MCP server to Cursor to query issues, trigger Seer root cause analysis, investigate database performance, and apply fixes — all without leaving your IDE.

- [Automate Weekly Performance Triage with Claude Code + Sentry MCP](https://sentry.io/cookbook/performance-bot-sentry-claude/): Use Claude Code scheduled tasks and the Sentry MCP server to automatically find your worst performance issues every week and create GitHub PRs with fixes.

## Testimonials

> Seer gives us exactly what we need — straight to the point, fast, and accurate. It’s saved us hours per feature, and that translates to the bottom line.

> — Marc Maciera Zayas, President @Honra

> Sentry [Seer] is actually… good?
One-shot fixed this error that I've spent the last 2 hours debugging

> — @aidenybai, 

> Seer provided insights that led us to a fix within 30 minutes, for a bug that would have taken an engineer at least a day otherwise.

> — Neil Wang, 

> Amazing. @getsentry Seer did better than I would have. I wouldn't have thought to have a special ogType for articles. https://t.co/Y44lHdMitM

> — @kentcdodds, 

---

*Source: [sentry.io/product/seer/](https://sentry.io/product/seer/)*
