Skip to main content

SentryAI Observability

Seer

Sentry's AI debugging agent finds root causes in issue and trace data, along with logs and profiles. It drafts fixes or hands them to coding agents. It also reviews pull requests on GitHub.com and GitLab.com.

The 30-Second Take

Add Seer if Sentry already holds your production telemetry and diagnosis is what slows your fixes.

Sentry's AI debugging agent finds a root cause from an issue's stack trace, traces, logs and linked GitHub or GitLab code. It then drafts a fix, opens a pull request or hands the plan to a Claude, Cursor or Copilot agent.

Best fit
Teams with code on GitHub.com or GitLab.com whose error backlog outgrows the engineers who triage it; Seer needs a paid Sentry plan.
Main constraint
US$40 per active contributor per month on top of the Sentry plan, and no support for Bitbucket, Azure DevOps, self-hosted Git, or self-hosted Sentry.
First move
Trial Seer on one project with automation stopped after root cause analysis. Count the diagnoses engineers accept.

Why

Watch the bill: US$40 per active contributor a month on top of the Sentry plan, counting anyone who opens two or more pull requests a month in a Seer-enabled repository. Teams had merged under half of the public pull requests Seer opened by October 2026.

Practitioner sentiment, leaders and teams+11 Mixed

28 practitioners, 57 sources reviewed, Updated Nov 1, 2026How this is measured

Read the GILD Review
Save a product your organization uses.Keep up with Seer without adding it to your stack.Visit Website
Operating stack
Agentic Software Development

Comparisons

How does Seer compare with the alternatives?

  1. Seer vs Claude Code

    • AI Debugging

    Use Seer to diagnose from production telemetry and Claude Code to implement and test the fix. Seer can run before anyone asks and hand its root cause to a Claude agent. Claude Code sees production through the tools you connect, such as Sentry's MCP server.

  2. Seer vs CodeRabbit

    • AI Code Review

    Choose Seer's review if your team already debugs production with Seer on GitHub.com or GitLab.com, since it comes inside the same per-contributor price as Autofix. Choose CodeRabbit for every major Git platform and reviews in the IDE and CLI.

Operator Insights

What are engineering leaders learning from deploying Seer?

Buying and deployment

What engineering leaders should verify before a broader rollout.

Sourced from Sentry documentation

How you buy it

US$40

Per active contributor per month, on top of a paid Sentry plan. Developer excludes Seer.

Source 1, Sentry, Seer pricing: Seer pricingSource 5, sentry.io, Sentry plans and pricing: Sentry plans and pricing

Details

Seer costs US$40 per active contributor per month on top of a paid Sentry plan, separate from pay-as-you-go. Team costs US$26 per month and Business US$80 per month, billed annually. The free Developer plan excludes Seer. Start a trial in subscription settings.

Cost drivers

2 pull requests

On GitHub, monthly; GitHub bots are excluded. GitLab counts every group member.

Source 1, Sentry, Seer pricing: Seer pricingSource 3, Sentry, Autofix: AutofixSource 8, Sentry, Claude Agent integration: Claude Agent integration

Details

On GitHub, anyone opening 2 or more pull requests a month in a Seer-enabled repository counts. Sentry excludes GitHub accounts marked [bot] and counts every GitLab group member. Coding-agent handoffs run on the agent's own account, such as your Anthropic API key for Claude Agent. Legacy pricing, US$20 per month with US$25 of Seer credits and then US$1 per fix run, closed to new subscribers in January 2026; Sentry says earlier subscribers are likely still on it.

Where it runs

GitHub or GitLab

Cloud-hosted repositories only, on Sentry SaaS in the US or EU. No self-hosting.

Source 6, docs.sentry.io, Data Storage Location (US or EU): Data Storage Location (US or EU)Source 2, Sentry, Seer: SeerSource 3, Sentry, Autofix: AutofixSource 7, develop.sentry.dev, Self-hosted Sentry: Self-hosted Sentry

Details

Seer runs in Sentry SaaS's US or EU region through the Sentry UI and Slack. It supports repositories on GitHub.com and GitLab.com only. It excludes self-hosted Sentry and self-hosted Git, plus Bitbucket and Azure DevOps. Coding-agent handoff and pull request iteration require GitHub.

What to verify

CVE-2026-90999

Published September 16, 2026 for automatic agent handoff. No vendor fix listed on October 28.

Source 4, Sentry, AI Privacy Principles: AI Privacy PrinciplesSource 9, sentry.io, Sentry subprocessors: Sentry subprocessorsSource 10, kb.cert.org, CERT/CC VU#212479: CERT/CC VU#212479

Details

Sentry trains generative AI models on your data only if you opt in. It lists Anthropic and OpenAI as US AI subprocessors. CERT/CC published CVE-2026-90999 on September 16, 2026 for automatic coding-agent handoff from public DSN events. On October 28, 2026, the note still listed no vendor fix.

Signals

What is the current evidence saying about Seer?

Engineering teams and open source maintainers report on Seer alongside individual developers. Each finding links to the public accounts behind it.

Whose sources count

Practitioner sentiment, leaders and teams

+11 Mixed net

of 29 sources that take a side, each author counted once. Small sample.

How this figure is made

Current sentiment

Positive, mixed and negative sources

The score counts them as 9 positive, 13 mixed and 6 negative votes, one per author.

29 team sources give an opinion: 10 positive, 13 mixed and 6 negative, and most of the mixed ones are bug reports from teams still using Seer. Code review divides between real catches and rejected or blocked reviews. Of the 6 discussing wrong findings, 5 raise them. All 6 discussing platform and setup limits report problems. Teams split on autonomous fixes.

Run a pilot on one production app to measure which failures it surfaces and how long tracing them takes.

Evidence field. All 57 sources, one mark each.

Arrange by

Each mark is one source: positive, mixed, negative, no opinion stated, or documentation (not counted).

By sentiment, Engineering leaders and teams. Every source GILD read, grouped as the field draws it.
GroupSourcesPositiveMixedNegativeNo opinion stated and not counted in the scoreDocumentation, checked and not counted
Positive10100000
Mixed13013000
Negative600600
Not counted200020
Documentation10000010
Outside this group16105100
Every source GILD read, by the quarter it was published, as the field's time axis counts it. Documentation is dated by the day it was checked.
QuarterSources
Q2 20252
Q3 20252
Q4 20254
Q1 20269
Q2 20269
Q3 202619
Q4 20262
Documentation, checked10

By sentiment

10 documentation pages check facts and are not counted; 16 sit outside this group.

Hover a mark for a quick look, click it or press Enter to open its source.Tap a mark to open its source, then step to its neighbors with Previous and Next.

What practitioners praise

Each mark is a source on it; filled marks praise it.

  1. Code Review Catches10 of 16 sources on it praise it

Most common concerns

Top concern of 2. Each mark is a source on it; filled marks raise it.

  1. Platform & Setup LimitsAll 6 sources on it raise it as a concern
All 57 sources behind these findings
  1. SeerSentry (Official), Product documentation, checked Oct 12, 2026
  2. AutofixSentry (Official), Product documentation, checked Oct 12, 2026
  3. Code ReviewSentry (Official), Product documentation, checked Oct 12, 2026
  4. Pricing & Billing: Seer pricingSentry (Official), Product documentation, checked Oct 12, 2026
  5. AI Privacy PrinciplesSentry (Official), Product documentation, checked Oct 12, 2026
  6. Service Data UsageSentry (Official), Product documentation, checked Oct 12, 2026
  7. Coding AgentsSentry (Official), Product documentation, checked Oct 12, 2026
  8. Claude AgentSentry (Official), Product documentation, checked Oct 12, 2026
  9. GitHub integrationSentry (Official), Product documentation, checked Oct 12, 2026
  10. AI in SentrySentry (Official), Product documentation, checked Oct 12, 2026
  11. sentry: pilot Seer root cause analysis without automatic pull requestsGustavo Valverde, Cloud and software architect, Zcash Foundation contributor (self-described: Zebra, the Zcash Foundation's Rust node, public repository), GitHub issue, published Oct 9, 2026
  12. Comment on: feat(analysis): require more confirmations for species rare at the locationgilindoesgit, Contributor to BirdNET-Go (self-described: BirdNET-Go, open-source bird sound analysis), GitHub pull request review comment, published Oct 3, 2026
  13. Seer is automatically opening PR's when "Show Generative AI Features" is enabled, also when you don't subscribe to SeerØyvind Andreassen, Developer at Elekt (self-described: Elekt internal repositories, no Seer subscription), GitHub issue, published Sep 29, 2026
  14. Comment on: fix: sentry issues fixesTimo Juonoja, Developer on the City of Helsinki's Linked Components UI (self-described: City of Helsinki, Linked Components UI), GitHub pull request review comment, published Sep 28, 2026
  15. The AI Revolution Fails without Psychological Safety for Developers: a Conversation with Erin DoyleErin Doyle, founding engineer at Quotient (Quotient, a small engineering team building an engineering productivity product), Podcast episode transcript, The InfoQ Podcast (The Architects Podcast), published Sep 28, 2026
  16. Epic: Sentry auto-fix: production errors to Shepherd fix PRs (Seer replacement)Patrick Lenz, Co-founder of erwins-enkel and head of top.media GmbH (self-described: Shepherd agent harness, pilot on the ltdovr flowagent project), GitHub issue, published Sep 24, 2026
  17. Autofix lock generation to be excluded or modifiableRainer Leit, Web developer (self-described: Team projects using pnpm), GitHub issue, published Sep 22, 2026
  18. fix(ios-ship): include run_attempt in cache keys (Seer P2 + P1)Jay Wedgeworth, Developer at Simple-With-Us (self-described: DealDex iOS release workflow), GitHub pull request, published Sep 18, 2026
  19. PhantomFix: a fabricated bug that hijacks an AI autofix agent (CVE-2026-90999)agyn, AI agent platform company; finding credited to Nikita Benkovich and Vitalii Valkov (self-described: Research on the team's own accounts and infrastructure), Security research, agyn blog, published Sep 14, 2026
  20. Sentry Triage: seed the fix hand-off with Sentry Seer AILiz Tom, Developer (self-described: Sentry triage extension for GitHub Copilot sessions), GitHub pull request, published Sep 11, 2026
  21. [BF] Sentry Max Features: Node Profiling, iOS Replay, Seer AutofixJay Wedgeworth, Developer at Simple-With-Us (self-described: BotFleet app on Sentry with sponsored credit), GitHub pull request, published Sep 4, 2026
  22. Comment on: feat: make an absent user identity something a caller has to stateGuilherme Pimenta, Developer at Topsort (self-described: Topsort Kotlin SDK), GitHub pull request review comment, published Aug 26, 2026
  23. Autonomous Autofix: automatically trigger Autofix on new high-priority issuesDistronode, Engineering account for Distronode Corporation (self-described: Distronode Corporation, GitLab and GitHub repositories), GitHub issue, published Aug 20, 2026
  24. Comment on: feat(dagster): add Sentry error tracking and harden failure alertingTobias Macey, Engineer at MIT Open Learning (self-described: MIT Open Learning data platform, Dagster pipelines), GitHub pull request review comment, published Aug 7, 2026
  25. Sign commits with Seer AutofixYohan Gracia, Developer at Wamiz (self-described: Wamiz, Seer as the Autofix handoff agent), GitHub issue, published Aug 4, 2026
  26. Probe: check whether Seer AI Code Review runs on this repoBen Atkinson, developer (self-described: Company repository django-stateless-mcp), GitHub pull request, published Jul 29, 2026
  27. Seer "deletage to agent" is not persisting / workingTristan Bessoussa, CTO at Wamiz (Nestlé) (self-described: Wamiz Sentry organization, Autofix handoff to Claude Agent), GitHub issue, published Jul 27, 2026
  28. Comment on: feat(mit-learn): Fastly edge in front of api.learn.mit.edu, raise webapp HPA capTobias Macey, Engineer at MIT Open Learning (self-described: MIT Open Learning infrastructure), GitHub pull request review comment, published Jul 21, 2026
  29. Comment on: fix: persist last selected org on the userGilad Resisi, Contributor to Postiz (self-described: Postiz, open-source social media scheduler), GitHub pull request review comment, published Jul 19, 2026
  30. Comment on: Seer GitLab integrationRaghu Saxena, developer (self-described: Seer Code Review on GitLab merge requests), GitHub issue comment, published Jul 13, 2026
  31. ci: review-gate: require only Seer + Codex (Copilot advisory)Evie Gauthier, Maintainer of CloudHub-Social Charm (self-described: CloudHub-Social Charm repository, bot review gate in CI), GitHub pull request, published Jul 9, 2026
  32. Add ability to delete or clear Seer Agent chat historyCartmanXT, Sentry user (self-described: Seer Agent conversations in a shared Sentry organization), GitHub issue, published Jun 26, 2026
  33. Comment on: ci(platform): gate E2E tests behind ci-ready PR labelNicholas Tindle, Open source maintainer of AutoGPT (self-described: AutoGPT repository, Seer code review on every pull request), GitHub pull request review comment, published Jun 25, 2026
  34. Comment on: Seer support for Azure DevopsMP-Steve, Sentry user on Azure DevOps (self-described: Evaluating Seer with repositories on Azure DevOps), GitHub issue comment, published Jun 22, 2026
  35. Seer Autofix: unable to delete repository from connected repositoriesstephanefv, Developer at Finverse (self-described: Finverse project with 12 GitLab repositories connected to Autofix), GitHub issue, published Jun 12, 2026
  36. Comment on: Seer GitLab integrationMatthew Jacobi, GitHub profile lists Oppian and Pitchup (self-described: Self-hosted GitLab EE with Sentry SaaS, GitLab Seer beta), GitHub issue comment, published Jun 12, 2026
  37. Comment on: Seer GitLab integrationBjorn, GitHub profile lists Norsk Test AS (self-described: Norsk Test AS, repositories on GitLab), GitHub issue comment, published May 13, 2026
  38. Comment on: Observability Stack: AI First?jblake, Hacker News commenter (self-described: Choosing an observability stack: Datadog for logs, Sentry for errors), Hacker News comment, published Apr 19, 2026
  39. SEER AI Code Review via MCP, SHIFT LEFT!Charlie, Sentry user (self-described: Team using Seer code review on pull requests), GitHub issue, published Apr 14, 2026
  40. Comment on: Switch from npm to pnpmorangemug, Developer at Oak National Academy (self-described: Oak National Academy web application), GitHub pull request review comment, published Apr 14, 2026
  41. Comment on: feat: add allowedAgents config for memory hooksRai Butera, Developer at RSTLSS, outside contributor (self-described: Contribution to supermemoryai/openclaw-supermemory), GitHub pull request comment, published Mar 18, 2026
  42. Comment on: fix(frontend): AutoPilot notification follow-upsKrzysztof Czerwinski, AutoGPT contributor (self-described: AutoGPT frontend, Seer code review), GitHub pull request review comment, published Mar 16, 2026
  43. Comment on: fix(backend/copilot): sync TranscriptBuilder with CLI on mid-stream compactionZamil Majdy, AutoGPT contributor (self-described: AutoGPT backend, Seer code review), GitHub pull request review comment, published Mar 13, 2026
  44. Comment on: fix(security): block global-flag merge bypassAndrew Rich, Engineer at Night Owl Studio (self-described: Own claude-config repository), GitHub pull request comment, published Feb 26, 2026
  45. Comment on: fix(backend): Extract binary files from ClaudeCodeBlock sandboxBently, AutoGPT maintainer (self-described: AutoGPT backend, Seer code review), GitHub pull request review comment, published Feb 17, 2026
  46. Cannot configure Seer when out of budgetPablo Parada, QA Lead at Deliverect (self-described: Deliverect's Sentry organization, Seer Autofix automation), GitHub issue, published Feb 4, 2026
  47. Post by Mickrich384Mickrich384, Sentry user, self-described, X post, published Jan 27, 2026
  48. Comment on: fix(windows): create .pth file to link bundled site-packagesjfichtner, Contributor to Aperant (self-described: Aperant repository reviewed by several AI reviewers), GitHub pull request comment, published Jan 14, 2026
  49. Comment on: substreams: initial implementationdanilo neves cruz, Engineer at Exactly (self-described: Exactly's exa repository, reviewed by Seer, Cursor, Gemini, and CodeRabbit), GitHub pull request review comment, published Jan 8, 2026
  50. Comment on: Update GitHub Enterprise Integration with the Latest GitHub Integration FeaturesDonald Gaeta, IT Software Developer at ARCH Medical (self-described: ARCH Medical, GitHub Enterprise Cloud connected to Sentry), GitHub issue comment, published Dec 2, 2025
  51. Comment on: Update the UniqueIdentifier copSeth Herr, Developer on Give Lively's RuboCop rules (self-described: Give Lively, shared RuboCop configuration), GitHub pull request review comment, published Oct 31, 2025
  52. Comment on: Support more standard objects in Record Page LayoutBaptiste Devessier, Contributor to Twenty (self-described: Twenty, open-source CRM), GitHub pull request review comment, published Oct 23, 2025
  53. Comment on: Observability - add new countersetiennejouan, Contributor to Twenty (self-described: Twenty, open-source CRM), GitHub pull request review comment, published Oct 23, 2025
  54. Post by @kentcdoddsKent C. Dodds, developer educator (self-described: Own website), X post, published Jul 12, 2025
  55. Exploring AI issue resolution with Sentry SeerJon Purvis, AI lead at Visualsoft (Visualsoft, UK ecommerce agency; Sentry user for years, Seer trial on its own applications), Company blog post, Visualsoft, published Jul 10, 2025
  56. Seer Bitbucket integrationmdawart, Sentry user requesting Bitbucket support (self-described: Repositories hosted on Bitbucket), GitHub issue, published May 27, 2025
  57. Post by @aidenybaiAiden Bai, open source developer (self-described: Own project), X post, published Apr 3, 2025

Apr 2025 to Oct 2026.

47 sources from practitioners, by month and sentiment.

The full readExplore all Seer Signals4 praise themes, 5 concerns, 3 points of agreement and 2 disagreements across all three groups, with all 57 sources open to inspect.

Where It Fits

Where does Seer belong in the stack?

Open Where It Fits: the Stack Field and the full map

Seer is Core across Validate and Operate, supports Build, and touches Plan and Ship.

Business area
Product & Engineering
Function
Software Development
Operating stack
Agentic Software Development
Primary role
AI Debugging Agent for Production Errors
Seer beside the rest of its stackThe Stack Field, every product on every layer
FootprintSeer across the Agentic Software Development stack. Bar height is its role on each layer.

  1. Plan

    1. Work planning: Touches

      Work planning, touches. Seer Agent prioritizes open issues and archives stale ones. The issue tracker remains the planning record.

  2. Build

    1. Codebase context: Supports

      Codebase context, supports. Seer reads repositories connected to each Sentry project, including distributed services across repositories. It parses rules files for Cursor, Windsurf, Cline, and Claude Code.

    2. Coding: Supports

      Coding, supports. Autofix generates fixes and opens GitHub or GitLab pull requests for issues Sentry captures. Coding agents handle feature work.

    3. Agent runtime: Touches

      Agent runtime, touches. Seer runs in the Sentry UI and Slack. Other agents access it from editors and terminals through Sentry's MCP server and CLI.

    4. Tool execution: Supports

      Tool execution, supports. Seer hands its root cause and plan to Claude, Cursor, or GitHub Copilot cloud agents. Seer Agent uses connectors to read Datadog and Google Cloud data.

  3. Validate

    1. Debugging: Core

      Debugging, core. Seer diagnoses root causes on demand or automatically. It follows an issue's stack trace and telemetry into the responsible code, using traces, logs, and profiles.

    2. Testing: Supports

      Testing, supports. On GitHub, Seer pushes follow-up commits for failing CI and adds regression tests when asked. Your team owns the test suite.

    3. Code review: Supports

      Code review, supports. Code Review predicts errors in ready-for-review pull requests on GitHub.com and GitLab.com. It reports a GitHub status check and works alongside human or dedicated tool reviews.

    4. Application security: Touches

      Application security, touches. Seer is not a security scanner, and its automatic handoff to coding agents is the subject of CVE-2026-90999, so security teams review its settings without relying on it.

  4. Ship

    1. Source control: Touches

      Source control, touches. Seer opens branches and pull requests through GitHub and GitLab integrations. The Git platform holds the authoritative record.

    2. CI/CD: Touches

      CI/CD, touches. Seer reads CI failures on its pull requests. Your CI system builds and tests the software and handles deployment.

  5. Operate

    1. Observability: Core

      Observability, core. Seer uses Sentry's error and trace data, along with logs and profiles. Teams steer Seer Agent's incident investigations in Slack.

Market mapThe layers Seer covers, and who else owns each one.

  1. Debugging & investigation

    CoreValidate

    • No other product we cover owns this layer

  2. Observability & incident response

    CoreOperate

    • Datadog
    • Sentry
    • PagerDuty

  3. Codebase context & intelligence

    SupportsBuild

  4. Coding & implementation

    SupportsBuild

  5. Tool execution & integrations

    SupportsBuild

7 more layers on the full map. Core, Supports and Touches describe coverage. They say nothing about quality.

More on Seer

  1. GILD ReviewGILD's evaluation, with the buying facts
  2. Research2 pieces
  3. Guides4 guides
  4. Operator Insights1 operator account
  5. Where It FitsOn the Agentic Software Development stack
  6. Related Products6 products