Baz CLI: Interactive code reviews

Today we are introducing the Baz CLI.

It features four core review modes: Walkthrough, Requirements, Comments & Chat. All aimed at one single goal: closing the coding loop.

Instead of producing reports, Baz CLI walks you through a change the way an experienced reviewer would. You start a review from the terminal, and Baz helps you understand what changed, why it matters, and what needs attention before merge.

Walk through the change

Most reviews fail before they even begin because reviewers do not understand the shape of the change. Large diffs, unfamiliar code, and cross cutting behavior make it hard to know where to focus.

Baz starts by walking through the change as a flow, not a file list. It explains what the change is doing, how different parts connect, and where behavior or usage may have shifted. This gives you a mental model before you look at details, which makes everything that follows faster and more accurate.

If something does not make sense, you can ask for clarification and drill into that part of the change. The walkthrough adapts as you explore.

Review against requirements

Code reviews are rarely just about correctness. They are about whether a change does what it was supposed to do.

With the Baz CLI, you can review a change against requirements and expectations directly. You can ask whether a requirement is satisfied, whether an edge case was handled, or whether the behavior aligns with the intended design. The reviewer reasons about the code in that context and surfaces gaps that are easy to miss when reading diffs line by line.

This is especially useful for changes that look correct locally but violate assumptions elsewhere in the system.

Ask questions and explore

Reviews are conversations, but most tooling turns them into slow comment threads. You leave a note, wait for a response, and often lose context by the time it comes back.

Baz keeps that conversation interactive. You can ask follow up questions, explore why a decision was made, or ask what would happen under different conditions. Instead of guessing or writing speculative comments, you can reason through the change while the context is still fresh.

This tight feedback loop helps reviewers converge on real issues faster and helps authors fix problems before anyone else is blocked.

Resolve comments

As reviews progress, it becomes harder to tell what is still open and what is already resolved. Threads pile up and signal gets buried in noise.

Baz helps focus the review on unresolved concerns that actually affect correctness or safety. The goal is not to generate more comments, but to help reviewers and authors reach a confident merge decision. When a concern is addressed, the review moves on.

Run reviews where you work

The Baz CLI runs in the terminal, where developers already spend their time. You can review changes locally before opening a PR, iterate during development, or run reviews as part of automation. Baz supports both hosted execution and local token based execution, so teams can choose the setup that fits their security and privacy needs.

We believe this kind of human in the loop interaction is where AI works best in code review. The system does the tedious work of reading, reasoning, and surfacing issues, while developers make the decisions that require judgment.

The result is a review process that is faster, clearer, and more reliable than static scans or comment driven workflows.

The Baz CLI is available today. You can install it, connect it to your repository, and run your first interactive reviews.