Every source behind the read

41 sources in Engineering leaders and teams, with product documentation Showing all 57 sources

1. Mixed

   Gustavo Valverde, Cloud and software architect, Zcash Foundation contributor

   sentry: pilot Seer root cause analysis without automatic pull requestsGitHub issue

   Plans a Seer pilot on Zebra with automation stopped before pull requests, because an automatic fix for a network-reachable crash in a public repository would disclose a vulnerability.

   Published Oct 9, 2026self-described: Zebra, the Zcash Foundation's Rust node, public repository

   Counts toward

   • Overall signal
   • Per-Contributor Price: Discussed without concern
   • Data & Automation Safety: Raised as a concern
   • A person checks Seer's output
   • Triage volume is the reason to automate
   • Should diagnosis run in Seer, or in a coding agent the team already uses?: Seer inside Sentry
   • How far should Seer act without a person starting it?: Stop at the diagnosis

   Published on

   Developer Communities

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Autofix automation capped at root cause or plan

2. Mixed

   Øyvind Andreassen, Developer at Elekt

   Seer is automatically opening PR's when "Show Generative AI Features" is enabled, also when you don't subscribe to SeerGitHub issue

   Seer opened a pull request on their team's internal repository although they had not subscribed or asked for one; support traced it to the Show Generative AI Features setting.

   Published Sep 29, 2026self-described: Elekt internal repositories, no Seer subscription

   Counts toward

   • Overall signal
   • Platform & Setup Limits: Raised as a concern
   • Unrequested Output: Raised as a concern
   • How far should Seer act without a person starting it?: Stop at the diagnosis

   Published on

   Developer Communities

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

3. Negative

   Timo Juonoja, Developer on the City of Helsinki's Linked Components UI

   Comment on: fix: sentry issues fixesGitHub pull request review comment

   Rejected two Seer findings rated high and critical severity on the same pull request, a TypeError on an undefined start time and on a missing nested property, as not bugs.

   Published Sep 28, 2026self-described: City of Helsinki, Linked Components UI

   Counts toward

   • Overall signal
   • Code Review Catches: Mixed or negative
   • Wrong Findings: Raised as a concern

   Published on

   Developer Communities

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Seer code review on a pull request fixing Sentry issues

4. Positive

   Erin Doyle, founding engineer at Quotient

   The AI Revolution Fails without Psychological Safety for Developers: a Conversation with Erin DoylePodcast episode transcript, The InfoQ Podcast (The Architects Podcast)

   Quotient's founding engineer reports that the team uses Sentry and asks Seer for help when alerts do not fire as expected or when she needs help analyzing the data. She reports that assistants like it mean the team no longer has to be expert in each tool's domain, and make it easier and quicker to connect and analyze things.

   "So for instance, we use Sentry and Sentry has a chatbot named Seer. And so I can now ask Sentry…"

   "Or maybe I set up the integration wrong or maybe I just need help analyzing my data. I can now go to that chatbot and get help with that."

   Published Sep 28, 2026Quotient, a small engineering team building an engineering productivity product

   Counts toward

   • Overall signal
   • Time to an Answer: Positive
   • Should diagnosis run in Seer, or in a coding agent the team already uses?: Seer inside Sentry

   Published on

   Talks & Podcasts

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Seer used as Sentry's built-in assistant for the team's own Sentry setup and data

5. Negative

   Patrick Lenz, Co-founder of erwins-enkel and head of top.media GmbH

   Epic: Sentry auto-fix: production errors to Shepherd fix PRs (Seer replacement)GitHub issue

   Decided to replace Seer with Shepherd's own fix pipeline because Seer is proprietary, costs US$40 per active contributor per month, and does not know the team's house rules.

   Published Sep 24, 2026self-described: Shepherd agent harness, pilot on the ltdovr flowagent project

   Not counted

   Its author co-founded erwins-enkel, which builds Shepherd, the fix pipeline this issue plans as Seer's replacement. Kept in the record; it takes part in no figure.

   Published on

   Developer Communities

   Who

   Technical leadership

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Seer at US$40 per active contributor per month

6. Mixed

   Rainer Leit, Web developer

   Autofix lock generation to be excluded or modifiableGitHub issue

   Every Autofix pull request adds a new package-lock.json to their team's pnpm projects, which they have to delete by hand from each one.

   Published Sep 22, 2026self-described: Team projects using pnpm

   Counts toward

   • Overall signal
   • Fix Quality: Mixed or negative

   Published on

   Developer Communities

   Who

   Very small team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Autofix pull requests

7. Negative

   agyn, AI agent platform company; finding credited to Nikita Benkovich and Vitalii Valkov

   PhantomFix: a fabricated bug that hijacks an AI autofix agent (CVE-2026-90999)Security research, agyn blog

   Reported a critical flaw: a fabricated error sent to a public DSN can pass through Seer's analysis to an automatic coding agent that runs attacker code; advises pausing the automated handoff.

   Published Sep 14, 2026self-described: Research on the team's own accounts and infrastructure

   Counts toward

   • Overall signal
   • Data & Automation Safety: Raised as a concern
   • Seer works with a coding agent
   • A person checks Seer's output
   • How far should Seer act without a person starting it?: Stop at the diagnosis

   Published on

   Engineering Blogs & Reviews

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Autofix with automatic handoff to a coding agent

8. Positive

   Guilherme Pimenta, Developer at Topsort

   Comment on: feat: make an absent user identity something a caller has to stateGitHub pull request review comment

   Confirmed and fixed Seer's finding that a deprecation hint would rewrite callers into code that crashes on a blank value.

   Published Aug 26, 2026self-described: Topsort Kotlin SDK

   Counts toward

   • Overall signal
   • Code Review Catches: Positive

   Published on

   Developer Communities

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Seer code review

9. Mixed

   Distronode, Engineering account for Distronode Corporation

   Autonomous Autofix: automatically trigger Autofix on new high-priority issuesGitHub issue

   Asked for Autofix to run on every new high-priority issue and open a GitLab or GitHub pull request without manual steps, under a policy with a review window before merge.

   Published Aug 20, 2026self-described: Distronode Corporation, GitLab and GitHub repositories

   Counts toward

   • Overall signal
   • Triage volume is the reason to automate
   • How far should Seer act without a person starting it?: Let it run

   Published on

   Developer Communities

   Who

   Professional team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Autofix

10. Positive

    Tobias Macey, Engineer at MIT Open Learning

    Comment on: feat(dagster): add Sentry error tracking and harden failure alertingGitHub pull request review comment

    Fixed four Seer findings on one pull request, including a sensor cursor that would have dropped failures permanently and a fingerprint mismatch that contradicted their own pull request description. The commenter declined one suggested fix as wrong for production alerting and implemented an alternative.

    Published Aug 7, 2026self-described: MIT Open Learning data platform, Dagster pipelines

    Counts toward

    • Overall signal
    • Code Review Catches: Positive
    • A person checks Seer's output

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer code review

11. Mixed

    Yohan Gracia, Developer at Wamiz

    Sign commits with Seer AutofixGitHub issue

    Their team uses Seer to write Autofix commits but cannot sign them, which they want for security; Sentry support confirmed it is not possible.

    Published Aug 4, 2026self-described: Wamiz, Seer as the Autofix handoff agent

    Counts toward

    • Overall signal
    • Platform & Setup Limits: Raised as a concern
    • Data & Automation Safety: Raised as a concern
    • Should diagnosis run in Seer, or in a coding agent the team already uses?: Seer inside Sentry

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Autofix

12. Positive

    Ben Atkinson, developer

    Probe: check whether Seer AI Code Review runs on this repoGitHub pull request

    Opened a probe pull request with deliberate logic and security flaws that passed the linters; Seer's code review ran and posted three findings.

    Published Jul 29, 2026self-described: Company repository django-stateless-mcp

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

13. Mixed

    Tristan Bessoussa, CTO at Wamiz (Nestlé)

    Seer "deletage to agent" is not persisting / workingGitHub issue

    Switching a project's Autofix handoff from Seer to the Claude Agent did not persist at the organization level; setting it per project worked.

    Published Jul 27, 2026self-described: Wamiz Sentry organization, Autofix handoff to Claude Agent

    Counts toward

    • Overall signal
    • Platform & Setup Limits: Raised as a concern
    • Seer works with a coding agent

    Published on

    Developer Communities

    Who

    Technical leadership

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Autofix handoff to Claude Agent

14. Positive

    Tobias Macey, Engineer at MIT Open Learning

    Comment on: feat(mit-learn): Fastly edge in front of api.learn.mit.edu, raise webapp HPA capGitHub pull request review comment

    Confirmed Seer's finding that an IP restriction would block all non-Fastly traffic before the DNS cutover, and gated it behind the same flag.

    Published Jul 21, 2026self-described: MIT Open Learning infrastructure

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer code review

15. Positive

    Evie Gauthier, Maintainer of CloudHub-Social Charm

    ci: review-gate: require only Seer + Codex (Copilot advisory)GitHub pull request

    Made Seer's code review check, with Codex, the required bot review gate on the project's pull requests after Copilot's monthly review credits kept running out.

    Published Jul 9, 2026self-described: CloudHub-Social Charm repository, bot review gate in CI

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Very small team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer Code Review check run

16. Negative

    Nicholas Tindle, Open source maintainer of AutoGPT

    Comment on: ci(platform): gate E2E tests behind ci-ready PR labelGitHub pull request review comment

    Checked a high-severity Seer finding about a CI trigger against GitHub's documentation, found it wrong, and resolved it as a verified false positive.

    Published Jun 25, 2026self-described: AutoGPT repository, Seer code review on every pull request

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Wrong Findings: Raised as a concern
    • A person checks Seer's output

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review, high-severity finding

17. Mixed

    stephanefv, Developer at Finverse

    Seer Autofix: unable to delete repository from connected repositoriesGitHub issue

    Could not disconnect a GitLab repository from Autofix after connecting 12 repositories past a limit of 8; Sentry shipped a rewritten settings backend that fixed it four days later.

    Published Jun 12, 2026self-described: Finverse project with 12 GitLab repositories connected to Autofix

    Counts toward

    • Overall signal
    • Platform & Setup Limits: Raised as a concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Autofix with GitLab

18. Mixed

    Matthew Jacobi, GitHub profile lists Oppian and Pitchup

    Comment on: Seer GitLab integrationGitHub issue comment

    Getting Autofix to run on the GitLab beta took about a developer-day of reading Sentry's source. The engine produced a correct fix and opened a merge request, but webhooks, repository connection, and setup screens broke along the way.

    Published Jun 12, 2026self-described: Self-hosted GitLab EE with Sentry SaaS, GitLab Seer beta

    Counts toward, pending a recheck

    • Overall signal
    • Fix Quality: Positive
    • Platform & Setup Limits: Raised as a concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Needs a recheck

    Observed on

    GitLab Seer beta, Autofix

19. Negative

    Bjorn, GitHub profile lists Norsk Test AS

    Comment on: Seer GitLab integrationGitHub issue comment

    Seer stopped running root cause analysis until a repository was configured, and GitLab repositories could not be selected, so the commenter canceled the team's Seer subscription.

    Published May 13, 2026self-described: Norsk Test AS, repositories on GitLab

    Counts toward nothing current

    Replaced by newer evidence. Kept in the source history with its scope stated; it takes part in no current figure.

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Out of date

    Observed on

    Seer on the issue page, GitLab repositories

20. Mixed

    Charlie, Sentry user

    SEER AI Code Review via MCP, SHIFT LEFT!GitHub issue

    Their team likes Sentry but finds Seer's pull request reviews slow, and wants the same review in the CLI or IDE before a commit to save CI cycles.

    Published Apr 14, 2026self-described: Team using Seer code review on pull requests

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Time to an Answer: Mixed or negative

    Published on

    Developer Communities

    Who

    Very small team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

21. Mixed

    orangemug, Developer at Oak National Academy

    Comment on: Switch from npm to pnpmGitHub pull request review comment

    First doubted Seer's finding that CI workflows lacked a Node.js setup step after a move to pnpm. A colleague checked the docs a month later, the team agreed it was a real catch, and fixed it.

    Published Apr 14, 2026self-described: Oak National Academy web application

    Counts toward

    • Overall signal
    • Code Review Catches: Positive
    • A person checks Seer's output

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer code review

22. Negative

    Krzysztof Czerwinski, AutoGPT contributor

    Comment on: fix(frontend): AutoPilot notification follow-upsGitHub pull request review comment

    Answered a Seer bug report on a notification change by explaining the flagged behavior was intended and did not indicate a bug.

    Published Mar 16, 2026self-described: AutoGPT frontend, Seer code review

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Wrong Findings: Raised as a concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

23. Mixed

    Zamil Majdy, AutoGPT contributor

    Comment on: fix(backend/copilot): sync TranscriptBuilder with CLI on mid-stream compactionGitHub pull request review comment

    On one pull request the commenter fixed two Seer findings and answered two others as intended behavior.

    Published Mar 13, 2026self-described: AutoGPT backend, Seer code review

    Counts toward

    • Overall signal
    • Code Review Catches: Positive
    • Wrong Findings: Discussed without concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

24. Positive

    Bently, AutoGPT maintainer

    Comment on: fix(backend): Extract binary files from ClaudeCodeBlock sandboxGitHub pull request review comment

    Fixed a high-severity Seer finding that text files were read into memory without the size check applied to binary files.

    Published Feb 17, 2026self-described: AutoGPT backend, Seer code review

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review, high-severity finding

25. Mixed

    Pablo Parada, QA Lead at Deliverect

    Cannot configure Seer when out of budgetGitHub issue

    Configured Autofix automation too aggressively, went over the Seer budget quickly, then could not change Seer settings until the next billing period; the issue was later closed as not planned.

    Published Feb 4, 2026self-described: Deliverect's Sentry organization, Seer Autofix automation

    Counts toward, pending a recheck

    • Overall signal
    • Per-Contributor Price: Raised as a concern
    • Unrequested Output: Discussed without concern
    • How far should Seer act without a person starting it?: Let it run

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Needs a recheck

    Observed on

    Per-run Seer billing, about US$1 per Autofix

26. Negative

    danilo neves cruz, Engineer at Exactly

    Comment on: substreams: initial implementationGitHub pull request review comment

    Pushed back on Seer findings as intended design on their team's pull request, where Seer reviewed alongside Cursor, Gemini, and CodeRabbit.

    Published Jan 8, 2026self-described: Exactly's exa repository, reviewed by Seer, Cursor, Gemini, and CodeRabbit

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Wrong Findings: Raised as a concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

27. Mixed

    Donald Gaeta, IT Software Developer at ARCH Medical

    Comment on: Update GitHub Enterprise Integration with the Latest GitHub Integration FeaturesGitHub issue comment

    On GitHub Enterprise Cloud their team could not use AI Code Review and other features Sentry advertises for GitHub.com; Sentry replied that Autofix had reached GitHub Enterprise and code review would follow.

    Published Dec 2, 2025self-described: ARCH Medical, GitHub Enterprise Cloud connected to Sentry

    Counts toward

    • Overall signal
    • Platform & Setup Limits: Raised as a concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    GitHub Enterprise integration

28. Negative

    Seth Herr, Developer on Give Lively's RuboCop rules

    Comment on: Update the UniqueIdentifier copGitHub pull request review comment

    Rejected a Seer finding marked critical with full confidence, explaining that the matcher it misread leaves out the final quote.

    Published Oct 31, 2025self-described: Give Lively, shared RuboCop configuration

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Wrong Findings: Raised as a concern

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    Seer code review

29. Positive

    Baptiste Devessier, Contributor to Twenty

    Comment on: Support more standard objects in Record Page LayoutGitHub pull request review comment

    Accepted Seer's finding that a layout dispatcher change stopped routing the Dashboard object to its renderer, and fixed it before merge.

    Published Oct 23, 2025self-described: Twenty, open-source CRM

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    Seer code review

30. Positive

    etiennejouan, Contributor to Twenty

    Comment on: Observability - add new countersGitHub pull request review comment

    Acted on Seer's finding that a webhook success counter also counted failed 4xx and 5xx calls, and renamed the metric before merge.

    Published Oct 23, 2025self-described: Twenty, open-source CRM

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Professional team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    Seer code review

31. Positive

    Jon Purvis, AI lead at Visualsoft

    Exploring AI issue resolution with Sentry SeerCompany blog post, Visualsoft

    Visualsoft's AI lead reports that in every case the team tested, Seer's first root cause guess was correct, and that the team merged several Seer pull requests after a person verified each fix. The team asked for pull requests that follow its own templates and for Seer to fix high actionability issues with no manual start.

    "In every case we tested, this initial attempt at working out the issue, was always correct."

    "After a human verified the fix, we were able to merge several of these pull requests into our codebase, ready for deployment."

    "Ideally, we would like Seer to handle high-actionability issues without any manual input."

    Published Jul 10, 2025Visualsoft, UK ecommerce agency; Sentry user for years, Seer trial on its own applications

    Counts toward, pending a recheck

    • Overall signal
    • Root Cause Analysis: Positive
    • Fix Quality: Positive
    • A person checks Seer's output
    • Should diagnosis run in Seer, or in a coding agent the team already uses?: Seer inside Sentry
    • How far should Seer act without a person starting it?: Let it run

    Published on

    Engineering Blogs & Reviews

    Who

    Technical leadership

    Evidence

    Reported

    Applies to

    Needs a recheck

    Observed on

    Seer root cause analysis and one-click fixes on high actionability issues

32. Positive

    gilindoesgit, Contributor to BirdNET-Go

    Comment on: feat(analysis): require more confirmations for species rare at the locationGitHub pull request review comment

    Fixed the validation-message bug Seer flagged, but found Seer's suggested fix would not have worked because the bands are sorted first, and added a test for that case.

    Published Oct 3, 2026self-described: BirdNET-Go, open-source bird sound analysis

    Counts toward

    • Overall signal
    • Code Review Catches: Positive
    • A person checks Seer's output

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer code review

33. Positive

    Jay Wedgeworth, Developer at Simple-With-Us

    fix(ios-ship): include run_attempt in cache keys (Seer P2 + P1)GitHub pull request

    Fixed two findings from Seer's code review that were missed before merge: a real cache-key bug on workflow reruns and a style rule from the repository's agent instructions.

    Published Sep 18, 2026self-described: DealDex iOS release workflow

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

34. Positive

    Liz Tom, Developer

    Sentry Triage: seed the fix hand-off with Sentry Seer AIGitHub pull request

    Passes Seer's root cause and fix plan into a Copilot fix session as untrusted advisory data, and treats the plan as a hypothesis to check before acting on it.

    Published Sep 11, 2026self-described: Sentry triage extension for GitHub Copilot sessions

    Counts toward

    • Overall signal
    • Data & Automation Safety: Discussed without concern
    • Seer works with a coding agent
    • A person checks Seer's output

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer explain and plan through the Sentry SDK

35. Positive

    Jay Wedgeworth, Developer at Simple-With-Us

    [BF] Sentry Max Features: Node Profiling, iOS Replay, Seer AutofixGitHub pull request

    Turned Autofix automation to always and enabled Seer's issue scanner for one app, holding it off on their other apps; billing did not block because of a sponsored credit.

    Published Sep 4, 2026self-described: BotFleet app on Sentry with sponsored credit

    Counts toward

    • Overall signal
    • Per-Contributor Price: Discussed without concern
    • Triage volume is the reason to automate
    • Should diagnosis run in Seer, or in a coding agent the team already uses?: Seer inside Sentry
    • How far should Seer act without a person starting it?: Let it run

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Autofix automation set to always; sponsored credit

36. Mixed

    Gilad Resisi, Contributor to Postiz

    Comment on: fix: persist last selected org on the userGitHub pull request review comment

    Across four Seer findings on one pull request, fixed one valid bug, called one pre-existing, declined one as adding cost without changing any outcome, and rejected one as not a bug.

    Published Jul 19, 2026self-described: Postiz, open-source social media scheduler

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Wrong Findings: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer code review

37. Mixed

    Raghu Saxena, developer

    Comment on: Seer GitLab integrationGitHub issue comment

    Seer code review jobs got stuck in GitLab pipelines with no way to cancel or retry them, which blocked merging until the commenter ran a new pipeline.

    Published Jul 13, 2026self-described: Seer Code Review on GitLab merge requests

    Counts toward

    • Overall signal
    • Code Review Catches: Mixed or negative
    • Platform & Setup Limits: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Code Review on GitLab

38. Mixed

    CartmanXT, Sentry user

    Add ability to delete or clear Seer Agent chat historyGitHub issue

    Asked for a way to delete Seer Agent conversations, because sensitive debugging sessions stay visible to everyone in the organization.

    Published Jun 26, 2026self-described: Seer Agent conversations in a shared Sentry organization

    Counts toward

    • Overall signal
    • Data & Automation Safety: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Seer Agent

39. Negative

    MP-Steve, Sentry user on Azure DevOps

    Comment on: Seer support for Azure DevopsGitHub issue comment

    Said their team was unlikely to buy Seer without Azure DevOps support; Sentry replied the next day that it had no update and was rolling out GitLab first.

    Published Jun 22, 2026self-described: Evaluating Seer with repositories on Azure DevOps

    Counts toward

    • Overall signal
    • Platform & Setup Limits: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

40. Mixed

    jblake, Hacker News commenter

    Comment on: Observability Stack: AI First?Hacker News comment

    Settling on Datadog for logs and Sentry for errors, the commenter found Seer interesting but unnecessary when they could send everything straight to Claude.

    Published Apr 19, 2026self-described: Choosing an observability stack: Datadog for logs, Sentry for errors

    Counts toward

    • Overall signal
    • Should diagnosis run in Seer, or in a coding agent the team already uses?: Their own agent

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

41. Positive

    Rai Butera, Developer at RSTLSS, outside contributor

    Comment on: feat: add allowedAgents config for memory hooksGitHub pull request comment

    Fixed an undefined session key edge case that Seer's review caught, adding regression tests before asking maintainers to merge.

    Published Mar 18, 2026self-described: Contribution to supermemoryai/openclaw-supermemory

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

42. Positive

    Andrew Rich, Engineer at Night Owl Studio

    Comment on: fix(security): block global-flag merge bypassGitHub pull request comment

    Fixed a regular expression bug Seer found in a security guard, where a character class matched && by accident, and added a test for chained commands.

    Published Feb 26, 2026self-described: Own claude-config repository

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review

43. Positive

    Mickrich384, Sentry user, self-described

    Post by Mickrich384X post

    Calls Seer really useful for teams already tracking bugs in Sentry: it digs into the codebase and gives its best guess at the cause.

    Published Jan 27, 2026

    Counts toward

    • Overall signal
    • Root Cause Analysis: Positive
    • A person checks Seer's output

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

44. Positive

    jfichtner, Contributor to Aperant

    Comment on: fix(windows): create .pth file to link bundled site-packagesGitHub pull request comment

    Of the feedback from several AI reviewers, the commenter listed Sentry's finding about absolute build-time paths as the one critical fix.

    Published Jan 14, 2026self-described: Aperant repository reviewed by several AI reviewers

    Counts toward

    • Overall signal
    • Code Review Catches: Positive

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Current

    Observed on

    AI Code Review alongside Gemini and CodeRabbit

45. Positive

    Kent C. Dodds, developer educator

    Post by @kentcdoddsX post

    Said Seer's fix did better than the author would have, adding a special Open Graph type for articles that the author would not have thought of.

    Published Jul 12, 2025self-described: Own website

    Counts toward

    • Overall signal
    • Fix Quality: Positive

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Still applicable

46. Mixed

    mdawart, Sentry user requesting Bitbucket support

    Seer Bitbucket integrationGitHub issue

    Asked for Seer Autofix on Bitbucket repositories; the thread collected requests from other Bitbucket users through January 2026 while Sentry gave rough timelines.

    Published May 27, 2025self-described: Repositories hosted on Bitbucket

    Counts toward

    • Overall signal
    • Platform & Setup Limits: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    Autofix

47. Positive

    Aiden Bai, open source developer

    Post by @aidenybaiX post

    Autofix fixed in one pass an error Bai had spent two hours debugging, and Bai wrote that they had been sleeping on the feature.

    Published Apr 3, 2025self-described: Own project

    Counts toward, pending a recheck

    • Overall signal
    • Fix Quality: Positive
    • Time to an Answer: Positive

    Published on

    Developer Communities

    Who

    Individual practitioner

    Evidence

    Reported

    Applies to

    Needs a recheck

    Observed on

    Autofix