Projects and sessions

Add local projects, use Git worktrees, and safely manage Sesori sessions.

Projects are folders on the computer running the Bridge. Sessions are assistant conversations attached to one of those folders.

Add a project

1. On the Projects screen, tap Add Project.
2. Browse folders on the connected computer.
3. Select Add as new project for the current folder, or use Create new folder first.
4. If the folder is not a Git repository, choose whether to enable Git tracking.

Enable Git is a consequential action: Sesori initializes Git when needed and commits all non-ignored files to create the baseline required for history and dedicated worktrees. Review the folder first. Choose Continue Without Git if you do not want Sesori to create that commit.

If Git setup cannot finish, the project still opens, but dedicated workspaces remain unavailable until the repository has an initial commit.

Folder access on macOS

The Bridge can browse only folders available to the process that launched it. If macOS blocks a location, grant Full Disk Access to the terminal app or managed Bridge process you actually use, then retry. Do not grant broader access to unrelated apps.

Discovered projects

Enabled assistants can report projects they already know. Discovery differs between assistants, so a folder may appear after you open or create a local session in that assistant. Add Project is the direct alternative when discovery does not find it.

Rename or hide a project

• Rename Project changes the project name shown by Sesori; it does not move the folder on disk.
• Hide Project removes the project from the list without deleting its folder, sessions, Git history, or assistant data.

If a project folder was moved or deleted, Sesori marks it unavailable. Restore the original path or hide the stale entry.

Create a session

Tap New session, choose a Coding tool, and select the options exposed by that assistant. Existing sessions keep their original assistant.

Dedicated workspace

Turn on Dedicated workspace to isolate a new session in its own Git worktree and branch. This helps parallel sessions avoid editing the same checkout.

Dedicated workspaces require a Git repository with at least one commit. Sesori falls back to the main project folder when the project is not Git-backed, has no commit, or worktree creation fails. Confirm the workspace and branch shown in the session before running parallel edits.

Session list actions

• Rename changes the title shown in Sesori.
• Mark as read / Mark as unread controls the unread state without changing the conversation.
• Archive permanently makes a session read-only. You can still view it under Show archived, but you cannot reopen it, send prompts, or unarchive it.
• Delete permanently removes the assistant session and Sesori's local transcript records through the Bridge.

Archive and delete cannot be undone. Read the confirmation sheet before continuing.

Prompt attachment files spilled to Sesori's shared local attachment directory can remain after session deletion. Clean that directory manually only when no other session or Bridge data directory references its files; see Remove the managed installation.

Worktree cleanup when deleting

For a dedicated-workspace session, the delete confirmation can offer Delete worktree. Cleanup refuses or warns about unsafe cases such as unstaged changes, a worktree shared by another active session, or an unexpected branch.

Deleting a worktree does not delete its Git branch. If you force deletion past a cleanup warning, review the listed risk first.

Next

👉 Sessions and chat