> For the complete documentation index, see [llms.txt](https://docs.baz.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.baz.co/capabilities/sessions.md).

# Sessions

<figure><img src="/files/r1TxR1tTfrwqrQ3OtpHQ" alt=""><figcaption></figcaption></figure>

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.

## 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.baz.co/capabilities/sessions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.