Automations on org repos still not triggering for personal accounts

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Same issue as Automations not triggering for organization repositories, which is now closed without a fix.

An automation with a “PR opened, by Me” trigger never fires for repos in a GitHub org. I opened a PR myself after creating the automation and no run showed up in Run History. Manual test runs against the same repo work fine and can comment on the PR, so repo access looks okay. It’s only the trigger that never fires.

Setup:

  • Personal Cursor account, no team
  • The Cursor GitHub app on the org was installed by an org admin, not me. I’m not an org admin, so I can’t re-authorize the installation.
  • The repos show up in the automation’s trigger picker

What I tried:

Steps to Reproduce

  1. On a personal Cursor account, create an automation with a “PR opened, by Me” trigger on a repo in a GitHub org whose Cursor app someone else installed
  2. Open a PR on that repo
  3. No run appears and nothing is logged

Expected Behavior

The automation runs, the same way it does for personal repos.

Operating System

MacOS

Version Information

IDE Cursor IDE 3.23.12

Additional Information

In the old thread, staff said the org’s GitHub app can stay tied to a team setup, so its webhooks can’t be matched to a personal automation, and suggested moving to a team account. That isn’t an option for me. Is there a way to get org webhooks to a personal automation, or a fix planned? I can share the org and repo privately.

Does this stop you from using Cursor

No - Cursor works, but with this issue

8

Hey @mikepitre, thanks for the detailed report, and for following up on the earlier thread.

We were able to reproduce this on our side with the same kind of setup. The PR events from your org are reaching us; the issue is how they’re matched to automations. Your org’s Cursor GitHub app is connected to a Cursor team, and PR events from that installation are currently only matched against automations owned by that team or its members. A personal automation outside that team never gets checked, so nothing shows up in Run History (manual Test runs take a different path, which is why those work). Reconnecting GitHub won’t change this, so you didn’t miss a step or misconfigure anything.

We’ve let the team know. No need to send the org or repo details, we have what we need.

In the meantime, two workarounds:

  1. Create the automation from a team account. If you have a Cursor account that’s a member of your org’s Cursor team (for example, under your work email), an automation created from that account will fire on your PRs. Runs from that automation use that account’s plan rather than your personal one.
  2. Use a webhook trigger. Add a Webhook trigger to your personal automation and call it from a GitHub Actions workflow on pull_request: opened, including the PR URL in the request body (the agent receives the payload). You’ll need permission to add a workflow file and a repository secret for the automation’s API key, and you’ll set the repo in the automation’s settings since webhook runs don’t pick it up from the PR. More on webhook triggers here: Automations

I’ll update this thread when there’s news on supporting personal automations here.

9

Thanks @kevinn, really appreciate you reproducing it and explaining what’s going on.

I’ll look at the workarounds in the meantime. Looking forward to the update when personal automations are supported for this.