Unable to configure triggers in Approver Agents

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

Using “label” as a trigger for an Approver Agent, I am unable to select the label to trigger on, or whether to trigger on the label being added or removed.

Steps to Reproduce

  1. In Cursor Web, under Bugbot > Approver Agents, create a new Approver Agent.
  2. Select “Label Change” as the trigger.
    1. Note that there are no options to set the label or add/remove trigger action.
  3. Configure the repository.
    1. The options still do not appear.
  4. Save and reload the page.
    1. The options still do not appear.

Expected Behavior

I would expect to be able to select:

  1. Which label the agent should be triggering on
  2. Whether the agent should trigger upon the label being added, or upon it being removed.

Screenshots / Screen Recordings

create agent.png
create agent.png2828×568 60.9 KB
add trigger.png
add trigger.png738×706 50.5 KB
configure trigger.png
configure trigger.png2268×562 44.6 KB

Operating System

MacOS

Version Information

I experienced this in the settings on Cursor Web (Chrome Version 150.0.7871.182).

For AI issues: which model did you use?

N/A

For AI issues: add Request ID with privacy disabled

N/A

Additional Information

I’m selecting “Cursor is unusable” below, because the Approver Agent is not usable, however, please note that Cursor itself still works perfectly fine, it is only the Approver Agent that is affected.
We are on the Team plan

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Thanks for the detailed report and screenshots @watsonben . I reproduced this on my end: the Label Change trigger row only lets you set the repository scope and who can trigger it, with no label name field and no add/remove selector, including after a save and reload.

Worth flagging so it doesn’t catch you off guard: an Approver Agent saved with this trigger currently matches any label added to a pull request in the repositories you’ve scoped, and won’t fire on label removal. If you need label-specific triggering today, the Automations builder at cursor.com/automations does expose the full label configuration. It’s a different surface than an Approver Agent, so it won’t give you the same approval behavior, but it works if the goal is to kick off an agent on one specific label.

None of this is caused by anything in your setup. I let the team know, and it’s an issue we’re tracking. I’ll post here when there’s an update. Thanks again for the report.