Automation cant set Origin Triggers

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

When creating an Automation, i cant add some Triggers for Origin.
These are:

  • Pull request
  • Comment added
  • New push to branch

Steps to Reproduce

  1. Create Automation
  2. Try to add an Origin Pull Request Trigger
  3. The Window will close

Expected Behavior

Being able to select all Origin Triggers

Operating System

Windows 10/11

Version Information

Its in the Cloud (cursor.com Website)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I reproduced it, and the issue is in the Add Trigger dropdown on the web dashboard. Nested submenus like Pull request collapse on hover or click, so the whole Origin block is basically not selectable with the mouse. It’s not just Origin, the same thing happens for other providers too. I’ve shared it with the team and we’re tracking it.

For now, two workarounds:

  • Type the trigger name into the search bar at the top of the Add Trigger menu like pull request or comment, then click the result. That path works.
  • Or use the arrow keys and Enter to navigate the menu instead of the mouse.

One note for later: automatic Pull request triggers for Origin repos are still rolling out, so even after you add them they might not fire automatically yet. Manual Run should work though.

Let me know if the workaround doesn’t help.

Hey @3_fabi_3 good news: the issue where the menu closed when selecting Origin triggers (Pull request, Comment added, New push to branch) is fixed, and the patch is already live on cursor.com. You don’t need to update anything, just try again.

One note from my last message still applies: automatic Pull request triggers for Origin repos are still rolling out, so even after you add them, they might not start firing right away. Manual Run works during this time.

Let me know if the menu is still closing.

Hey, the issue got not fully fixed. Now i can select other trigger methods, but not any Origin Pullrequest trigger method. I mean you said i can use them, but there are not reliable right ?

The UI Bug fixed only 50% of Buttons not reachable.
To summerize:
Fixed half:
Menü closes when trying to select a Origin Pullrequesting trigger.
But now it works to select all other Origin Triggers.

Hey, thanks for coming back with details. You’re right, the previous fix only covered part of it.

What’s happening now: the second-level menu is fixed, so Origin Comment added and New push to branch can now be selected with the mouse. But Pull request opens another, third-level submenu (Opened / Pushed / Merged / Draft opened), and that one still collapses on hover. That’s why you still can’t add an Origin Pull request trigger with the mouse.

Until this is fixed, you can still add an Origin Pull request trigger in two ways:

  • Type the exact trigger in the search at the top of the Add Trigger menu, like pull request opened, then click the flat result.
  • Or use the keyboard to navigate the menu: arrow keys to move, right arrow to open the submenu, Enter to select.

On reliability, there are two separate things. The menu issue is one thing, but automatic firing of Pull request triggers for Origin repos is still rolling out, so even after you add them, they might not fire right away. Manual Run works normally during this time.

Let me know if you were able to add the trigger via search or the keyboard.

I was able to get it with search and keyboard done.
I would also to give you a short Bug too.
When using any Cursor Model (Grok and Composer) first time for a new Project, without Fast Mode.
It visualises while Chatting always as Fast. Many users have reported this, but its still not fixed, why..?

Great that search and keyboard worked.

Good news, we also fixed the mouse part. The third-level Pull request submenu should no longer close on hover. This is on cursor.com’s side, so you don’t need to update anything. Please do a hard reload Ctrl+Shift+R or Cmd+Shift+R, then try adding the Origin Pull request trigger with the mouse. It should work.

On the second point about Fast, this is a known issue we’re tracking. The part related to the web picker on cursor.com/agents, where Fast turns itself back on after the first response, was recently fixed. It’s worth checking again after a hard reload too.

To narrow it down, can you confirm a couple things, ideally in a separate thread so it doesn’t get mixed with the triggers topic:

  • Where do you see this, web cursor.com/agents or the desktop IDE?
  • Which model, and if possible the Request ID or a link to the agent where Fast shows up instead of the option you selected.

There’s already an active thread on this exact issue, feel free to join it here: Cloud Agents always start in fast mode in web

Let me know how the trigger test goes after the reload.