I’ve been exploring the features and have encountered several frustrating errors:
Something very strange happens when connecting my GitHub repository (mgomez for testing) or my colleague’s (alejandro with the live repositories). A third person appears, whom we don’t know and who has no connection to the project. This person is named “ajmariduena”.
Even though the repositories are connected, none of the triggers for our test automations work. Neither does the BugBot trigger for testing the functionality.
When invoking BugBot with “@cursor review”, I get the error “Skipping Bugbot: Bugbot is disabled for this repository. Visit the Bugbot dashboard to update your settings.”
Regarding automations, commenting out the keyword that triggers an automation in GitHub doesn’t activate it.
If I run an automation, I get the error "Failed to test pull request automation
I have the same issue. I can prompt the automation with a “test run” and supply my PR number to get it to run, but even then it has some error about the pull request automation. And no matter what, I never get a trigger from GH to actually automatically activate it.
Hey, thanks for the detailed report. Let me address each point:
Unknown user “ajmariduena” appearing
That’s concerning. The team is aware of cases where old GitHub usernames can stick around in connected repos. Could you share a screenshot showing exactly where this user appears? Also, has anyone on your team ever had a different GitHub account connected to Cursor?
BugBot “disabled for this repository” error
BugBot has to be enabled per repo in your dashboard. Go to https://cursor.com/dashboard?tab=bugbot, open the BugBot tab, and make sure it’s toggled on for that repo. Also, BugBot is available on Teams and Individual (paid) plans, it may not be available on the Free plan.
Automation triggers not firing + “Failed to test pull request automation”
This is a known issue the team is tracking. It affects both GitHub event triggers not firing and test runs failing. No ETA yet, but your report and Ben_Miller’s confirmation help with prioritization. We’ll update this thread when there’s progress.
Could you also share:
Your Cursor version
Whether the automation is team-owned or private
A screenshot of your automation trigger configuration
This user, “ajmariduena,” appears everywhere/in every view related to GitHub. Neither my colleague nor I have ever heard of this user. Only my colleague’s GitHub is connected; every time we disconnect it, both our GitHub accounts disconnect, and when it reconnects, ajmariduena reappears.
We already have it active; we have an active, paid individual plan. I’m sharing a screenshot (this mysterious user even reappears ). But simply activating it with @cursor review causes the error I mentioned to reappear.
Hey, I’m looking at the screenshots. A couple of things:
About ajmariduena
In the Tools & MCP screenshot, GitHub is connected as alejandrorbradford to the orgs ajmariduena and the other one. That likely means ajmariduena is a GitHub organization that alejandrorbradford has access to on GitHub. Please check on GitHub by going to Settings > Organizations for alejandrorbradford. If ajmariduena is listed there, that explains why it shows up.
If alejandrorbradford is definitely not in the ajmariduena org, then it’s a bug and we’ll need to clean up the connection manually on the backend. Let me know.
BugBot is disabled
In the BugBot dashboard screenshot, ajmariduena shows 1 Repository, 0 Enabled. You need to click Enable next to that account and enable BugBot for the repo you need. Or, if your working repo is under the other org that’s blurred, make sure BugBot is enabled for the exact repo where you run @cursor review.
Automation triggers
Like I said earlier, this is a known issue on our side and the team is aware. For now, please use a manual test run with the PR number.
One more thing. In our system I see the account is on the Free plan. You mentioned an active paid individual plan, so maybe the subscription is on a different email. If so, make sure you’re signing into the dashboard with the right account.
Tell me how it looks for item 1 and we’ll go from there.
). But simply activating it with 