Code Correctness
Logical bugs, breaking changes, and type issues, traced to the consumers they break, in any repository.
AI Code Review
Review confirms quality. It doesn't create it.
Five focused agents review every change with the plan, the codebase, and your team's rules in view, all reading the same commit, pinned by object id. Fewer comments, stronger evidence. Evaluating alternatives? Compare Baz and Bugbot.
What makes a Baz review worth reading
Core review runs as five consolidated agents, with the Verification Agent and Fixer alongside. Verification starts below the diff: at the immutable objects the change is made of.
- ContextThe commit resolved once, plus the plan, the ticket, and consumers across repositories
- ReviewFive focused agents read the change in parallel
- ReflectWeak findings dropped, duplicates folded into one
- RecordA session shows what ran, read, and skipped
- ResolveFixer commits the fix, Merger calls the merge
Verification Agent
Checks each requirement from the ticket and design, and can run the app before it judges.
Verified at the object, not the checkout
Baz resolves the branch once, then reads trees and blobs by object id over the standard git protocol. Every agent judges the same snapshot, and other repositories are read without a clone.
Security that investigates
Cyber-capable models that prove exploitability. See Security Review.
Your standards, enforced
Your CLAUDE.md, AGENTS.md, and Skills, verified on every change. See Standards & Conventions.
Less noise by design
Weak findings are dropped and duplicates fold into one comment.
A record of every run
Every review is a session: what ran, what it read, and why.
One review workspace
Walkthrough, new commits only, threads, and merge status in one view.
Fixes, not just findings
Fixer commits the fix from the comment, checked in a sandbox first.
From scattered comments to one clear review
Review as correctionReview as confirmation
Reads the diff, one file at a timeReads the exact commit in context: plan, consumers, runtime, ownership
Judges whatever the branch points to right nowA verdict tied to one commit id; if the branch moves, the new head is reviewed
Eleven bots, overlapping commentsFive focused agents, duplicates folded into one comment
A verdict you take on faithA session that shows what ran, what it read, and why
Reread the whole PR after every pushReview only the commits since your last pass
Questions teams ask first
What happened to Review Sessions and the Review Workspace?
They are part of every review now, so they live here.
Why five agents instead of eleven?
Broader agents read the change once instead of competing for the same lines. Memories carry over.
Does Baz clone our repositories to review them?
No. Baz speaks the standard git wire protocol and fetches only the trees and blobs a review touches, by object id. History stays on your server, and nothing there needs to change.
Which code hosts does Baz review?
GitHub, GitLab, and Azure DevOps, including GitHub Enterprise Server.
Make review a confirmation, not a correction
Connect a repository and the agents review with full context from day one. Want them tuned to your standards first? Talk to us.