Feature Request: Allow Team Members to Flag False Positives in Bug Reports

Feature request for product/service

BugBot

Describe the request

Summary

Add the ability for team members (and optionally the broader community) to flag BugBot-reported issues as false positives directly from the bug report interface. This creates a feedback loop that helps the Cursor team continuously improve BugBot’s detection accuracy.

Problem

BugBot currently surfaces bug reports automatically, but there is no built-in mechanism to distinguish genuine bugs from false positives. As a result:

  • The bug queue can get polluted with noise, making it harder to prioritize real issues
  • There is no structured way for team members (who have the best context) to mark an issue as “not a bug”
  • BugBot has no feedback signal to learn from and improve over time

Proposed Solution

  1. Flag as False Positive button — Add a “Flag as False Positive” action on each BugBot-generated report, accessible to team members / trusted users
  2. Reason field — When flagging, prompt the user to select a reason (e.g., “Expected behavior”, “Already fixed”, “Out of scope”, “Cannot reproduce”) and optionally add a free-text note
  3. Confidence scoring — Aggregate flags across team members to assign a confidence score to each report (e.g., 2+ flags = likely false positive)
  4. Dashboard / filter — Allow filtering the bug list to hide or highlight flagged issues so the team can focus on high-confidence bugs
  5. Feedback loop to BugBot — Use the accumulated false-positive flags as training signal to reduce recurrence of similar false positives in the future

Why Team Members?

Team members have direct context about the codebase, intended behavior, and release state — they are best positioned to quickly assess whether a reported issue is a real bug or expected behavior. Empowering them to flag false positives keeps the bug queue clean and reduces triage overhead.

Expected Benefits

  • Cleaner, higher-signal bug queue
  • Faster triage and prioritization
  • Continuous improvement of BugBot accuracy over time
  • Reduced developer fatigue from investigating non-issues

Operating System (if it applies)

MacOS