> For the complete documentation index, see [llms.txt](https://docs.sesori.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sesori.com/user-guide/reviewing-changes.md).

# Review local changes

Inspect the local Git diff, branch, and pull-request status for a Sesori session.

Sesori can show the local files changed during a Git-backed session. Use this view to understand the assistant's work before you commit, push, or merge it from your normal development workflow.

## Open File Changes

Open a session and select **File Changes**. The summary shows the number of changed files, additions, and deletions. Expand a file to inspect its diff.

Sesori can label a file when:

* It is binary and has no text diff.
* The diff is too large to display.
* The Bridge could not read it.

Retry after the Bridge reconnects if the view fails to load.

## Understand the baseline

File Changes is a local Git diff supplied by the Bridge. It is independent of which assistant created the session.

* A dedicated workspace uses its worktree and branch as the session context.
* A session in the main project folder can include changes made by other tools or sessions in that same checkout.
* A non-Git project, or a repository without an initial commit, has no reliable Git baseline and may not offer a diff.

{% hint style="info" %}
The diff is a review surface, not a complete code-review or test result. Binary files, very large diffs, generated files, untracked state, and changes outside the session's baseline may need local inspection.
{% endhint %}

## Branch and pull-request status

Session rows can show the current branch and linked pull-request status when the Bridge can detect them. Sesori refreshes that status while you view a project; a Bridge setting controls the refresh interval.

Sesori currently monitors this Git and GitHub state. It does not commit, push, open, approve, or merge a pull request for you.

## Before you finish

On your computer:

1. Review the full working tree with your normal Git tools.
2. Run the project's tests, linting, and build checks.
3. Inspect any security- or data-sensitive change outside the mobile summary.
4. Commit, push, and open or merge the pull request through your normal workflow.

For dedicated sessions, decide whether to keep or remove the worktree when deleting the session. Sesori never deletes the branch automatically.


---

# 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.sesori.com/user-guide/reviewing-changes.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.