> 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/navigating-the-app.md).

# Main workflow

Sesori is organized around projects on your computer and the AI coding sessions inside them.

## Projects

The first screen lists projects known to the connected Bridge. A project can come from assistant discovery or from **Add Project**, which lets you browse the computer and register a folder yourself.

Each row can show the project name, local path, recent activity, and session or pull-request status. Tap a project to open its sessions. See [Projects and sessions](/user-guide/projects-and-sessions.md) for Git setup, dedicated workspaces, rename, and hide behavior.

## Session list

A session remains attached to the assistant that created it. From the list, you can:

* Open an existing session.
* Tap **New session** and choose a **Coding tool**.
* Review the branch and pull-request status Sesori can detect.
* Mark a session as read or unread.
* Rename, archive, or delete a session.
* Use **Show archived** to read permanently archived sessions.

Swipe actions and menus change with the session state. Destructive actions ask for confirmation.

## Session chat

The chat streams output from the assistant on your computer. You can type or dictate prompts, attach images when supported, queue follow-up messages, stop the current turn, and respond to questions or permissions.

Models, agents, slash commands, background tasks, and controls depend on the selected assistant. [Sessions and chat](/user-guide/sessions-and-chat.md) covers these differences.

## Local changes

Open **File Changes** for a Git-backed session to inspect the files changed from its local baseline. This is a read-only view of local diffs; Sesori does not commit or merge the changes for you.

See [Review local changes](/user-guide/reviewing-changes.md).

## Settings

Use Settings for:

* **Harnesses:** install, authenticate, enable, disable, refresh, or restart supported assistants.
* **Notifications:** choose AI interaction, session message, connection status, and system update notifications.
* **Bridge:** configure YOLO mode and the pull-request refresh interval when a compatible Bridge is connected.
* **Account:** see the current sign-in and log out.

{% hint style="warning" %}
YOLO mode automatically approves all permission requests routed through the Bridge. Read [Security and privacy](/get-started/security-and-privacy.md) before enabling it.
{% endhint %}

## Connection states

* **Green Bridge indicator:** the app can reach the Bridge.
* **Red Bridge indicator:** start `sesori-bridge` and keep the computer awake and online.
* **Project unavailable:** the local folder was moved or deleted; restore it or hide the project.
* **Harness needs attention:** open **Settings → Harnesses** and follow its setup action.

## Next

👉 [Projects and sessions](/user-guide/projects-and-sessions.md)


---

# 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/navigating-the-app.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.