Navigating the Sesori app: projects, sessions, and chat
A tour of every screen in Sesori — connect, project list, session list, and chat — for OpenCode, Codex, and Cursor sessions.
Sesori has four main screens. You move through them from top to bottom: sign in, pick a project, pick or create a session, then work in chat.
The four main screens
1. Connect
The entry point. Sign in with GitHub, Google, Apple, or email — using the same account you used in the Bridge.
What you can do here:
Sign in with GitHub, Google, Apple, or email.
Wait for the Bridge to come online.
Retry if authorization fails.
2. Project List
After you connect, you see every project available from your AI coding assistant — whichever of OpenCode, Codex, or Cursor you're running. Projects are folders — typically, each one is a codebase the assistant has been pointed at. When new assistants are added, they'll show up here the same way.
Project rows show the folder path, recent update time, and active-session count when a session is currently busy.
Tap a project to see its sessions.
3. Session List
Each project has its own list of AI coding sessions. You'll see:
Session title.
When it was last active.
A short preview of the last message.
Whether the session is archived.
What you can do here:
Tap a session to open it.
Tap New session to create a fresh session.
Open a session's menu to rename it, mark it read or unread, archive or unarchive it, or delete it.
Toggle archived sessions on or off.
4. Session Chat
The core screen — this is where you spend most of your time. Sessions and Chat covers it in depth.
Persistent UI
Two elements sit on top of whichever screen you're viewing:
Bridge status indicator
A small dot that shows whether the Sesori Bridge on your laptop or desktop is online.
🟢 Green — Bridge is online, ready to serve requests.
🔴 Red — Bridge is offline. Start
sesori-bridgeon your laptop or desktop.
Only appears when you're signed in and connected through the relay.
Connection overlay
A thin bar at the top of the app showing your current connection state. Tap it to:
Reconnect if the relay drops.
Disconnect and return to sign-in.
See when the Bridge is offline.
Settings
Open Settings from the app's main navigation. The sections appear in this order:
Account
Your profile and the option to sign out.
Notifications
Four toggles:
AI Interactions — questions and permission requests from active AI sessions.
Session Messages — new assistant messages from running sessions.
Connection Status — Bridge online and offline status changes.
System Updates — app and Bridge updates or maintenance notices.
Harnesses
Per-assistant setup and controls. See Harnesses below.
Bridge
Contains Pull request refresh, which sets how often viewed projects refresh pull request status.
Appearance
Choose Light, Dark, or System.
Chat input
Voice first — the composer rests as a hold-to-talk pill.
Text first — the composer rests as a tap-to-type field with the microphone alongside.
Support
Legal
Harnesses screen
The Harnesses screen is reachable from Settings → Harnesses, and also from the Coding tool selector when creating a session.
Each assistant shows a Setup status: Ready, Runtime missing, Authentication required, Unavailable, Not inspected, or Unknown. Once setup is ready, it also shows a Runtime status, and once running, a Work status of idle or busy.
Controls vary by assistant:
Enabled toggle — turn the assistant on or off.
Refresh setup — re-check the assistant's setup status.
Restart — restart the assistant process.
Idle timeout — set a per-assistant timeout, or tap Use bridge default to clear the override and fall back to the Bridge default.
A Bridge Default section at the bottom sets a Default idle timeout applied to every assistant that supports it.
If you disable or restart an assistant that is mid-task, Sesori asks you to confirm first, warning that active work may be interrupted.
An assistant whose process is controlled outside Sesori shows Managed outside Sesori instead of those controls. Sesori won't start, stop, restart, or suspend it.
Empty and error states
No projects — The assistant is running but doesn't have any projects registered. Open your AI coding assistant on your laptop or desktop inside a project folder.
Bridge offline — The Bridge CLI isn't running on your laptop or desktop, or it can't reach the relay. See troubleshooting.
Permission request — The assistant needs permission to run a command. Sesori surfaces these as a modal; approve or deny to continue.
Project directory not found — The folder was renamed or deleted on your machine. Go back, open the correct folder in the assistant, then refresh.
Next
👉 Sessions and Chat — where the work actually happens.
Last updated
Was this helpful?