Request for Repository/Org-Level Control over PR Summaries

Ideas Feature Requests
, ,
1

Feature request for product/service

BugBot

Describe the request

Hello Cursor BugBot Team,

We are currently using BugBot via GitHub Actions in a large-scale mono-repo environment. While we value the automated insights, the current implementation of PR Summaries is causing significant infrastructure strain for our team.

The Problem
When a Pull Request is opened, BugBot triggers and edits the PR description to add a summary. This “Edited” event re-triggers our entire GitHub Actions workflow suite. Because we operate in a heavy mono-repo, these redundant CI runs are:

Increasing our CI/CD costs significantly.

Causing queue delays for the rest of the engineering org.

Creating a “feedback loop” where bot edits compete with status checks.

Why standard workarounds don’t work for us
User Settings: While individual users can disable summaries, we cannot enforce this across a large team of contributors to protect our infrastructure.

Webhook Filtering: We cannot remove the types: [edited] trigger from our workflows, as we rely on that event for legitimate target_branch updates and manual PR revisions.

Feature Request
We would like to request the ability to disable PR Summaries at the Repository or Organization level.

Preferred implementation options:

Repository Setting: A toggle within the BugBot dashboard or a config file (e.g., .cursor/bugbot.json) to disable summaries globally for that repo.

Organization Setting: A top-level policy to disable summaries for all repos under our enterprise/org account.

Action Input: An option in the GitHub Action YAML (e.g., with: summaries: false) to suppress the edit event.

We love the core functionality of BugBot and want to keep using it, but we need a way to manage its impact on our CI load.

Looking forward to your thoughts on this.

Best regards,
Idan Shamam| Devops Engineer | Starkware

4

Hey Idan,

This is actually already possible! Your team admins need to:

  1. Go to https://cursor.com/en-US/dashboard/bugbot
  2. Toggle “Show all team repositories”
  3. Click into the installation
  4. Change the PR Summary setting. You can turn it off entirely, or switch it to “As Comment” which posts the summary as a comment instead of editing the PR description

“As Comment” is probably what you want. It won’t fire the edited event so your CI won’t re-trigger, but you still get the summary.

This is an admin-only setting so you’ll need one of your team owners to flip it.

6

Hey Colin,

Thanks for your reply. I walked through your instructions with one of our team admins, but we couldn’t find the “Toggle Show all team repositories” option, or anything related to that setting.

What should we try next?

8

I believe that since my original post, Show All Team Repositories has been renamed Show All Team Organizations.