Sessions
Sessions provide visibility into every Baz review execution.
While Pull Requests focus on review results, Sessions focus on how those results were produced. They show the reviewers that ran, the code they analyzed, the findings they generated, and the execution path that led to the final review.
Session Timeline
Each stage represents a step in the review pipeline.
| Stage | Function |
|---|---|
| Review Started | Review request received |
| Enriched Diff | Files and context collected |
| Agents | Reviewers analyze the change |
| Findings | Issues generated |
| Reflection | Findings validated and refined |
| Comment Merge | Overlapping findings consolidated |
| Review Completed | Results published |
Enriched Diff
The Enriched Diff stage shows the exact files reviewed by Baz.
It includes the modified files, change size, and review scope used during analysis.
Findings
The Findings stage displays issues generated during review.
From here you can see:
- Which findings were created
- Their severity
- Whether they were published
- How they contributed to the final review outcome
Reflection
Before publishing findings, Baz performs a reflection pass.
This stage reevaluates generated findings to improve quality and reduce unnecessary noise before comments are posted.
Comment Merge
Multiple reviewers may identify the same issue.
The Comment Merge stage consolidates overlapping findings into a single comment, reducing duplication while preserving review context.
Supported run types
Sessions are not limited to the PR reviewer flow. Every agent run type Baz executes is captured as a session, whether it runs against a pull request or against an entire repository. Each session shows a traceable timeline of what the agent did, which tools it used, and how the run ended.
| Run type | Scope | What the session shows |
|---|---|---|
| PR Review | Pull request | Reviewers, enriched diff, findings, reflection, comment merge |
| Planner | Pull request | Invocation, tool calls, the final plan, events, and stats |
| Merger | Pull request | Merge invocation, tool calls, and outcome |
| Spec Reviewer | Pull request | Spec context gathered, tool calls, and findings against requirements |
| Advanced Security Scan | Repository | Full-codebase scan invocation, tool calls, and findings, with no PR required |
- Planner sessions trace how a plan was generated: the initial invocation, every tool call the agent made while investigating the codebase, the final plan it produced, and the events and stats for the run.
- Merger sessions trace how Baz merged changes, including the tools invoked and the resulting outcome.
- Spec Reviewer sessions trace how requirements were checked against the code, including the context gathered and the findings produced.
- Advanced Security Scan sessions run against a full repository instead of a single pull request. They trace the scan from invocation through tool calls to findings, so repo-wide security runs are just as inspectable as a PR-scoped review.
Monitoring Active Reviews
Sessions can be used as a live execution dashboard.
While a review is running, the timeline provides visibility into:
- Current execution stage
- Review progress
- Generated findings
- Long-running or blocked steps
This makes it easy to understand what Baz is doing without waiting for the review to finish.