agentboards.org
Board/Code review agents/Bito AI Code Review Agent

Bito AI Code Review Agent

#149 overall#17 code review agentverified Sep 3, 2026v5.3.0

Codebase-aware AI code reviews for GitHub, GitLab and Bitbucket pull requests, with IDE extensions, a CLI and a self-hosted option

Key differences

Codebase-aware AI code reviews for GitHub, GitLab and Bitbucket pull requests, with IDE extensions, a CLI and a self-hosted option

  • Runs cloud. Team $12/seat/month and Professional $20/seat/month billed annually ($15 and $25 monthly), each with 5K reviewed lines per seat and $5 per extra 1K lines; 14-day free trial; self-hosted add-on $5/seat; Enterprise custom
  • Acts as an MCP server. Listed for 8 of 34 tools in this category.
  • Supports headless CI workflows. Listed for 33 of 34 tools in this category.

“Packaged in the Arch User Repository, so at least one Arch user has had a pull request reviewed.”

Website Docs 550 starsCompare vs…Dispute a fact
Appeal a claim or request ownership transfer

What it is

Bito's AI Code Review Agent posts context-aware review comments and fix suggestions on pull requests in GitHub, GitLab and Bitbucket (cloud and self-managed), folding in findings from static analysis and vulnerability tools such as fbinfer and Dependency-Check. It also runs inside VS Code, Cursor, Windsurf and JetBrains, from a CLI or GitHub Actions, and can be self-hosted; its companion AI Architect exposes a codebase knowledge graph to coding agents over MCP.

Specification

Source verification

Row snapshot checked 2026-09-03. Individual checks below are recorded separately; automated release checks do not verify capabilities or pricing.

pricing
Needs individual review
capabilities
Needs individual review
models
Needs individual review
protocols
Needs individual review
install
Needs individual review
license
Needs individual review

Architecture

Type
Code review agent
Runssrc ↗
cloud
Platforms
web, macos, linux, windows
Context windowsrc ↗
not documented
Languages
any

Models

Backbonesrc ↗
Claude
Bring your own model
No
Local models
No

Protocols

MCP clientsrc ↗
No
MCP server
Yes
OpenAPI tools
No

Capabilities

Terminal commandssrc ↗
No
Multi-file edits
No
Git operations
Yes
Browser control
No
Sandboxed execution
No
Multi-agent
No
Headless / CI
Yes

Cost

Modelsrc ↗
seat
Starts at
$12/mo
Free tier
No
Bring your own key
No

Team $12/seat/month and Professional $20/seat/month billed annually ($15 and $25 monthly), each with 5K reviewed lines per seat and $5 per extra 1K lines; 14-day free trial; self-hosted add-on $5/seat; Enterprise custom

Openness

Open sourcesrc ↗
No
License
proprietary
First release
2023-01
code-reviewpull-requestsstatic-analysisself-hostedide-extensionclimcpenterprise

Los Agentes on Bito AI Code Review Agent

Who are they?
The ruling
El JuezThe judge

El Amigo at 6.75 and El Hacker at 3.75 disagree about ownership, and El Crítico raises the thing that bills either way: the meter counts reviewed lines.

Adopt with conditions
Reasoning and trade-offs · AI analysis

El Amigo scores it highest for Bitbucket and self-managed GitLab. El Hacker scores it 3.75 because the reviewer is closed and runs on Claude only. El Crítico raises the cost neither of them scored: the meter is reviewed lines, so a regenerated lockfile bills like a feature.

El Hacker is overruled; a review bot is a service, not a tool you own. El Amigo wins for teams off GitHub, with La Jefa's $720 a month and SSO reserved for Enterprise as the cost of entry. Adopt with conditions, the condition being lockfiles and vendored directories excluded before the first billing cycle.

Agree with El Juez?
El AmigoThe friend

Pick Bito if your code lives on Bitbucket or self-managed GitLab and you want static analysis findings folded into the same review; pick CodeRabbit on GitHub.

6.8
Reasoning and trade-offs · AI analysis

You will like Bito if you are the team on Bitbucket or self-managed GitLab that every other reviewer treats as an afterthought; it covers GitHub, GitLab and Bitbucket including the self-managed variants, which for a regulated shop is the whole decision. The comments are dense, and you will spend week one turning categories off until the signal shows through. After that it is a steady second reader.

Pick it for a mixed-host shop or an on-premises Git server. Pick CodeRabbit if you are on GitHub and want the larger ecosystem of integrations.

reliability
7
usefulness
7
cost
6
longevity
7
Agree with El Amigo?
El CríticoThe critic

The meter is reviewed lines: 5K per seat per month, then $5 per extra thousand, so a regenerated lockfile or a vendored dependency bills like a feature.

5.8
Reasoning and trade-offs · AI analysis

The risk is the meter. Each seat includes 5K reviewed lines a month and every extra thousand costs $5. Lines are the wrong unit: a formatter run, a generated client, or a lockfile bump consumes quota and produces nothing worth reading, so the bill tracks churn rather than value, and the months with the most refactoring are the months with the biggest overage.

Exclude generated paths before the first invoice, because the tool bills what it sees. What it does right: fbinfer and Dependency-Check findings are folded into the same review, so part of every comment thread is deterministic and reproducible.

reliability
6
usefulness
6
cost
4
longevity
7
Agree with El Crítico?
El ProfesorThe professor

Context comes from symbol indexing, ASTs and embeddings, which is a principled design; the 89%, 34% and 87% figures on the overview page come with no method.

5.8
Reasoning and trade-offs · AI analysis

The documented context model has three layers: 1. symbol indexing, 2. abstract syntax trees, 3. embeddings, feeding specialized reviewers for performance, structure, security, optimization and scalability. That is more than diff-only tools do, and the layering is principled: symbols for precision, embeddings for recall, trees for structure. The same page claims merges sped up 89%, regressions cut 34% and 87% human-grade feedback, with no cohort, baseline or rater described.

Claimed, not demonstrated. What would change the assessment is a description of who was measured against what. The observation: two-digit precision on a number with no denominator.

reliability
6
usefulness
5
cost
6
longevity
6
Agree with El Profesor?
La InversoraThe investor

A 2023 assistant that found its product in review and is now selling a second one, the AI Architect knowledge graph, on usage pricing; a company looking for its second act.

6.0
Reasoning and trade-offs · AI analysis

Bito shipped in January 2023 as an assistant and pivoted into review when that market opened, which reads as adaptive rather than accidental, and adaptive is what a small company needs to be. The tell is AI Architect: a codebase knowledge graph sold usage-based to coding agents, a second product launched before the first has pricing power, which splits a small roadmap two ways.

Likely acquirer: Atlassian, given the Bitbucket coverage rivals ignore and a buyer that needs a reviewer of its own. Position: small; watch which product gets the roadmap and whether the graph finds its own customers.

reliability
6
usefulness
6
cost
6
longevity
6
Agree with La Inversora?
La JefaThe CTO

Sixty Team seats is $720 a month on annual, SSO and SAML are Enterprise only, self-hosting is a $5 per seat add-on, and SOC 2 Type II is on the page.

6.3
Reasoning and trade-offs · AI analysis

The demo is a review comment that cites the right file. Procurement: Team is $12 a seat on annual, so $720 a month for sixty, or $1,200 on Professional, the tier with Jira and Confluence. Self-hosted is a $5 per seat add-on, another $300, which is cheap for a deployment security will prefer. SSO and SAML sit in Enterprise, so the cheap tiers assume shared logins. SOC 2 Type II is stated.

Onboarding is a Git app install and a config file per repo. Approved with conditions: an Enterprise quote for SSO, and self-hosted if the questionnaire asks where the diff goes.

reliability
6
usefulness
6
cost
6
longevity
7
Agree with La Jefa?
El HackerThe tinkerer

Closed reviewer on Claude only, no key of mine, but the CLI is on GitHub, bito-cra.properties is a real config file, and the AI Architect graph is served to my agents over MCP.

3.8
Reasoning and trade-offs · AI analysis

No source, no BYOK, Claude chosen for me, and nothing runs on my box. The handles are real, though: the CLI lives at gitbito/CLI on GitHub, the review agent is customized through a bito-cra.properties file I can commit next to the code, and AI Architect exposes the codebase knowledge graph as an MCP server, so Claude Code or Cline can ask it where a symbol lives without me pasting paths.

That last part I would actually use, since a graph I can query from my own agent is worth more than a reviewer I cannot read. The rest is rented. Grudging respect for the properties file.

reliability
3
usefulness
5
cost
3
longevity
4
Agree with El Hacker?