The @cursor review and bugbot run commands have stopped triggering code reviews on my private GitHub account. While other agent commands (e.g., @cursor hello) work as expected, the specialized review pipeline remains non-responsive on this specific account. This issue persists even though my enterprise GitHub account—linked to a different Cursor installation—continues to work correctly.
Steps to Reproduce
Steps to Reproduce
Link a private GitHub account and an enterprise GitHub account to Cursor.
Open a Pull Request in a repository owned by the private GitHub account.
Comment @cursor review or bugbot run on the PR.
Observe that no “eyes” () reaction appears and no review is generated, despite the bot responding to non-review commands like @cursor hello.
Expected Behavior
Commenting @cursor review or bugbot run should trigger the Bugbot review pipeline, leading to an initial emoji reaction followed by inline code review comments.
Hey, thanks for the report. I’ll need a bit more info:
What plan are you on, Individual or Teams?
Is Bugbot not working on your own PRs, or on PRs from other contributors in the repo?
Are the repos enabled for Bugbot in the dashboard?
Context: On the Individual plan, Bugbot only works on PRs you opened yourself. To review PRs from teammates, you need the Teams plan. Based on the symptoms (it works on an enterprise account but not on a private one), this might be related.
Also experiencing this - was working perfectly last week with a ‘cursor review’ comment on any PR, now no eyes emoji or any indication of review beginning.
If you are on the individual plan of Bugbot Pro, then they have changed this behaviour recently that only if the PR author is the same as the user with the plan, then only the command works. I know it sucks but the only way now is to get a team plan for every user which is annoying when PR review products like Bugbot should be a usage-based plan and not user/seat based.
As a suggestion, maybe the cursor team can revisit the pricing of bugbot coz $40 for just reviews is kinda a lot, and a lot more expensive if working in teams (especially for smaller startups the costs add up, when the regular cursor subscription itself is $60-200 for power users and then paying another $40 for reviews).
In general the total operating costs for Cursor are adding up a lot lately, I would hope that we get some models (like their in-house Composer model) are truly unlimited or atleast rate limited within a timeframe or day. External models is understandable that they charge at the API pricing but in-house models should atleast be somewhat unlimited.
It previously worked perfectly on pull requests from all team members, that is why I confidently decided to upgrade to a yearly subscription. And now they changed this behavior and don’t reply to my refund request email
How can I get a reimbursement? Like you can’t simply go ahead and change terms of conditions or functionality in the app AFTER I have paid and been a user for months. I understand if changes occur AFTER my subscription expires and I have to renew. But during my subscription period – this is just malpractice.
I don’t want work with a company that just simply nerfs the app randomly when terms have been agreed. It’s really rude and bad business practice.
) reaction appears and no review is generated, despite the bot responding to non-review commands like @cursor hello.
