I’ve set up an automation to run bugbot when a PR is opened on one of my bitbucket cloud repostiories. As new PR’s are being opened, bugbot is not running. I tried cursor review verbose=true and bugbot run verbose=true in the comments of the PR and get nothing back. I’ve confirmed the cursor app is installed in my bitbucket workspace, and the automation is pointing at the correct repository. If I test the automation by pasting in a PR, it adds comments.
Hey @Josh_Luth1, thanks for the detailed report. I took a look on our side, and there are two separate things going on.
1. Bugbot isn’t turned on for your Bitbucket repositories yet
Your Cursor app is installed and linked correctly, and your pull request events are reaching us. Bugbot is enabled per repository, though, and it isn’t switched on for any of your Bitbucket Cloud repos right now. That’s why bugbot run and cursor review comments aren’t getting a response.
Find your Bitbucket workspace in the list and open it.
Enable Bugbot on the repositories you want reviewed.
Open a new PR, or comment bugbot run on an existing one.
From there, Bugbot reviews new PRs automatically. It also reads any .cursor/BUGBOT.md files in your repo, so review rules you keep there carry over. If you see an error when enabling a repo, reply here with the exact message.
2. Bitbucket PR triggers on custom automations aren’t starting runs right now
This isn’t something you misconfigured. PR-based triggers like “PR opened” on Bitbucket Cloud automations currently don’t start runs, even though the editor lets you save them and the Test button works. We’ve let the team know, and I’ll post here when I have an update.
Once Bugbot is enabled, it should cover most of what those automations were doing for PR reviews. You may want to pause them so you don’t end up with two sets of review comments on the same PR down the road.
Thanks Kevin… the bugbot config was hidden behind the setup apparently. Now that I’ve “completed” clicking those buttons I see the bugbot config you are referring to. All I saw before were the custom automations.