+1 for me here… Bitbucket integration is a must for us. I would hate to have to switch to Github at this point.
+1 for Bitbucket support! My team is completely on the Atlassian stack, and we would love to start using Cloud Agents and Bugbot. Right now, the GitHub/GitLab requirement is the only thing blocking our team-wide adoption of Cursor.
+1 please, let us, bitbucket users, enter this world of modernity where cars can fly and nuclear energy can fit in a smartwatch
Right now you only have Github/lab support. When will Bitbucket be added?
Adding another voice: Bitbucket-native Bugbot + Background Agents would be a big deal for us. Our dev work is in Cursor but the whole review/CI workflow is on Bitbucket, so today we either review PRs by hand or maintain our own MCP-based glue. Inline PR review comments, agent triggers from a PR, and thread replies via the Bitbucket API (Cloud and Data Center, with app-password/token auth for SSO) would close the gap. Lots of enterprise teams are in the same boat. Happy to beta test.
+1 please add Bitbucket support
+1 — and our blocker is getting more painful by the month.
Our org is all-in on the Atlassian stack, with Bitbucket as our source of truth for 18 developers across 2 teams. We’re paying Cursor users and love the editor, but the lack of Bitbucket support is now actively walling us off from a huge and growing share of what we’re paying for. Because almost everything is built on top of the Cloud Agent platform — which only connects to GitHub/GitLab — we’re locked out of:
- Cloud Agents — the core blocker. They clone/push via GitHub or GitLab, so our whole team is out.
- Bugbot (and Bugbot Autofix) — GitHub/GitLab only.
- Slack integration — blocked; it’s just a front-end to Cloud Agents and requires connecting GitHub/GitLab first.
- Jira integration — we’re on the Atlassian stack, but we can’t launch agents from Jira issues because it requires a GitHub/GitLab connection for PRs.
- Cursor Review / PR Inbox / Merge Queue — GitHub-based.
- Automations (PR triggers/tools) and Fix CI Failures — gated behind GitHub/GitLab (CI autofix is GitHub Actions only).
- Web & mobile agents — just launch surfaces for Cloud Agents, so blocked too.
We even tried Cursor’s own “My Machines” / self-hosted agents as a workaround — hoping we could point a worker at our local Bitbucket checkout and run (and Slack-trigger) Cloud Agents on our own compute. No luck: self-hosting only changes where the agent runs, not which provider Cursor integrates with. The repo connection and every trigger surface (e.g. Slack) still demand a GitHub or GitLab connection, so we were locked out exactly as before.
The hard part isn’t that these features don’t exist — it’s watching a steady stream of genuinely great releases land every few weeks, knowing our team can’t touch any of them purely because of where our code lives. That gap between “what Cursor can do” and “what we’re allowed to use” keeps widening, and it’s getting harder to justify expanding seats (or to fend off the internal “should we just migrate / look at another tool?” conversation).
We’re not asking for full parity on day one. Even a minimal Bitbucket connector that unblocks Cloud Agents would massively expand our usage. Please prioritize this — there’s clearly a large, paying, enterprise audience in this thread ready to adopt the moment it ships.
Happy to be a design partner / beta tester if that helps.
+1 — we’re a team on Bitbucket and this blocks us from using Cloud Agents/Bugbot which would make cursor an even bigger force multiplier for us than it already is.
Hey, thanks for the detailed feedback, especially the breakdown of the blocked features. It’s really helpful to see it all in one place.
The Bitbucket request is on our radar, and this thread is one of the clearest signals on it, so the team is seeing it. I can’t share an exact timeline yet. Right now we officially support GitHub and GitLab.
As soon as we have anything concrete on Bitbucket, we’ll post an update in this thread. Thanks for staying in touch and for sharing more details. Knowing which specific workflows are critical for you really helps.
Pleaaaaase