Automations not triggering for organization repositories (works for personal repos)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

•	Automations only fail for organization repositories
•	They work as expected for personal repositories
•	The GitHub App for Cursor is already installed in the organization
•	Previously, Cursor was part of the organization team, and Automations worked correctly at that time
•	Recently, I switched to using a personal account instead of the organization account
•	Since switching accounts, Automations no longer trigger for organization repositories

Steps to Reproduce

  1. Connect a GitHub account to Cursor
    2. Ensure Cursor GitHub App is installed on both:
    • a personal repository
    • an organization repository
    3. Create or configure an Automation in Cursor (e.g., trigger on issue creation or PR events)
    4. In a personal repository:
    • Create an issue or PR that should trigger the Automation
    • Confirm that the Automation runs successfully
    5. In an organization repository:
    • Create an issue or PR with the same conditions
    • Observe that the Automation does not trigger

Additional context for reproduction:
6. Previously, the Cursor account was part of the organization team
7. Switch the Cursor connection to a personal account (not in the organization team)
8. Repeat steps 4–5 and observe the issue persists only for organization repositories

Expected Behavior

Automations should trigger consistently for both personal and organization repositories when the same conditions are met, as long as the Cursor GitHub App is properly installed and authorized.

Switching from an organization account to a personal account should not affect Automation behavior for organization repositories that already have the Cursor GitHub App installed.

Operating System

MacOS

Version Information

Version: 2.7.0-pre.140.patch.0
VSCode Version: 1.105.1
Commit: ccfa72ce1f439af527c44b009c67fb94169b1100
Date: 2026-03-26T01:58:51.913Z
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. This is a known issue. When switching from a team account to a personal one, webhook auth for org repos can break. A few users have hit similar behavior:

I’ve shared this with the team. No ETA yet, but your report helps with prioritization.

Sadly, there isn’t an easy workaround. It’s on the server-side webhook authorization. If you can use a team account for org repos, that should avoid the issue.

Let me know if you have any questions.