Most AI review tools skip Bitbucket entirely. Git AutoReview covers Cloud, Server, and Data Center — with human-in-the-loop approval so nothing lands on your PR without you signing off. Five minutes from install to first review, and your code never leaves your machine.
The setup differs depending on your Bitbucket flavour. Pick yours and we'll show exactly what you need.
Select your Bitbucket platform:
Hosted by Atlassian at bitbucket.org. Authentication uses App Passwords (legacy) or the newer API Tokens — both work with Git AutoReview.
Scopes needed: Account: Read, Repositories: Read, Write, Pull requests: Read, Write.
We tested every major AI code review tool against Bitbucket in April 2026. The results weren't close.
| Feature | Git AutoReview | CodeRabbit | Qodo | Bito |
|---|---|---|---|---|
Bitbucket Cloud | ||||
Bitbucket Server Qodo: via self-hosted PR-Agent only | ||||
Bitbucket Data Center Qodo: via self-hosted PR-Agent only | ||||
Human-in-the-loop Approve each suggestion before posting | ||||
BYOK (bring your own key) | ||||
Multi-model (Claude, Gemini, GPT) | ||||
VS Code native | ||||
Works behind firewall |
Last verified April 2026. Qodo supports BB Server/DC only through self-hosted PR-Agent.
See full comparisons →Cloud uses App Passwords or the newer API Tokens. Both work — API Tokens are workspace-scoped while App Passwords are account-wide. Here's the path with API Tokens (recommended for new setups).
bitbucket.org hosted service
Server and Data Center share the same REST API, so the setup is identical. The only difference: for DC, use your load-balancer URL instead of a single-node address.
Self-hosted Bitbucket (v7.x+) or enterprise cluster
Step-by-step screenshots showing exactly how to create an API token with the right permissions for Git AutoReview.
Give it a descriptive name like "Git AR - BB". Tokens last up to 365 days.

Choose the Bitbucket app to access repository and pull request APIs.

Search "repo" and select read:repository:bitbucket and write:repository:bitbucket.

Search "pull" and select read:pullrequest:bitbucket and write:pullrequest:bitbucket.

Verify all 4 scopes are selected, then create the token. Copy it immediately — you won't see it again.

Track your progress — checks persist in your browser so you can come back anytime.
These are the four that tend to bite first-timers. Worth scanning before you start so the install runs clean on the first try.
App Passwords need Account Read + Repo Read/Write + PR Read/Write. Missing any one of these and the extension can't post review comments.
Cloud has both. App Passwords are account-level (older), API Tokens are workspace-scoped (newer). Both work with Git AutoReview — pick whichever your workspace admin prefers.
If your Bitbucket instance uses a custom certificate authority, add the CA cert to your OS trust store. VS Code inherits system certificates — no extension config needed.
Cloud asks for workspace slug + repo slug. Server/DC asks for project key + repo slug. They look similar but aren't interchangeable — check your Bitbucket URL path.
Bitbucket has roughly 10 million developers, and until Git AutoReview shipped, not one AI review tool covered all three deployment models. CodeRabbit and Bito never added it. Qodo Merge supports Server/DC only if you self-host their PR-Agent — Cloud is still out. That left a sizable gap we decided was worth filling.
The harder engineering problem was Data Center. DC nodes sit behind load balancers that rotate requests unpredictably, and the webhook delivery semantics differ from Cloud's. We tested against an actual clustered DC instance instead of mocking the API — clustering changes how state is read across requests, and you only see the failure modes when nodes disagree mid-write. That's why our DC support behaves the same in production as it does in a single-node test.
Human-in-the-loop approval lands differently on Bitbucket than on GitHub or GitLab. A lot of Bitbucket Server and Data Center installs are inside regulated industries — finance, healthcare, government — where an AI dropping comments on a PR autonomously is a compliance question, not a feature request. Our flow keeps every suggestion in VS Code first: review, edit or discard what doesn't fit, then publish. Developers stay in control and the audit trail stays clean.
Setup takes 5 minutes. Free tier: 3 reviews/day (10/day after email registration). No credit card required.