Security Review Agent Issue adding Repo as Trigger

Support Bug Reports
, , ,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

When adding triggers to the Security Reviewer agent for repos in our GitHub organization, behavior is inconsistent across team members that have the same permissions (member permissions). One user is able to add their repo to the security reviewer agent, and another gets an interesting error: “Send to Slack is enabled, but Slack is not connected”

Steps to Reproduce

Steps to Reproduce

  1. Go to Cursor Dashboard → Security Reviewer → Add Trigger
  2. Attempt to select an org-owned GitHub repo
  3. Select Save
  4. Notice that the slack related error appears

Expected Behavior

When the user clicks save, their repo is successfully added as a trigger to the security agent.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Cursor Web Application

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

I can confirm this is a bug on our end, not a permissions issue. When “Send to Slack” is turned on for the Security Reviewer, saving the agent runs a Slack-connection check against whoever is doing the save - even if you’re only adding a repo trigger. So a teammate who has personally connected Slack can save fine, while a teammate who hasn’t gets “Send to Slack is enabled but Slack is not connected.” That lines up exactly with the inconsistency you’re seeing.

A few ways to unblock in the meantime:

  1. Connect Slack for the blocked member: on the Security Reviewer page, click Connect next to Send to Slack (or use Integrations & MCP in the dashboard), then save. Once connected, adding the repo goes through.
  2. Have the teammate who can already save make the repo-trigger change, since saving works for them.
  3. Temporarily toggle off Send to Slack on the agent, add the repo trigger, save, then turn Send to Slack back on.

I’ve reported this to our team so an unrelated edit like adding a repo isn’t blocked by each member’s personal Slack connection. I’ll follow up here when there’s an update!