AI Walkthroughs
When a PR opens, Baz generates a structured walkthrough that explains the change in terms of intent, architecture, and impact - divided into implementation sections that link directly to the relevant area in the diff.
Product
Add Planner to the Integrations flow by wiring a new provider entry into the config, the IntegrationType model union, and the router so the Settings → Integrations tooling section surfaces the card. Provide a dedicated Planner page built from the shared IntegrationPage components and CodeBlock, describing the plugin setup for Claude Code, Codex, and Cursor plus the MCP installation guidance.
<div className="flex flex-col gap-2"> <h3>Cursor</h3> <CodeBlock code={CURSOR_INSTALL} /> </div> <hr className="my-4 border-divider" /> <div className="flex flex-col gap-2"> <h3>MCP</h3> <McpReferral to="/settings/integrations/mcp" /> </div>e54f10e added an MCP section pointing to the existing MCP integration setup. ✓ <IntegrationDocsLink href={PLUGIN_DOCS} />What's inside
The interface is built around continuous review rather than one-time approval. Baz tracks review state as the pull request evolves, so reviewers focus only on what changed since the last pass.
When a PR opens, Baz generates a structured walkthrough that explains the change in terms of intent, architecture, and impact - divided into implementation sections that link directly to the relevant area in the diff.
The operational summary of the PR: open reviewer comments, external comments, checks passed, and merge blockers - so you immediately see whether the PR is ready to merge.
Organizes all modified files hierarchically with added/removed lines, review indicators, and directory grouping, making high-impact and high-churn areas immediately visible.
Tracks reviewed and unreviewed commits automatically, so during active cycles you focus only on changes introduced since the previous review pass instead of rereading the whole PR.
Centralizes all review discussions. Each finding includes file and line references, resolution state, fix prompts, and Cursor integration to send fixes directly into your editor.
Aggregates every merge requirement into one view - CI checks, approval requirements, open review threads, and outstanding merge blockers.
Structured reports generated inside the PR: requirement validation, evidence references, file and line mappings, findings, and severity classification - each actionable and connected to the relevant code.
Get started
Bring walkthroughs, comments, checks, and merge readiness into a single workspace. Sign up to connect a repo, or talk to us about rolling it out across your org.