Connect the Sesori app to OpenCode, Codex, or Cursor
Sign in, connect to the Bridge, and pick OpenCode, Codex, or Cursor for your first session. Additional assistants are planned.
Sesori connects to your AI coding assistant — OpenCode, Codex, or Cursor — through the Bridge running on your laptop or desktop.
Prerequisites
Before connecting:
Your AI coding assistant must be installed and working locally.
The Bridge must be running on your laptop or desktop.
You must sign in with the same account in both places.
1. Sign in
Open Sesori and sign in with the account you used for the Bridge. You can use:
GitHub
Google
Apple
Email
Use the same account you used when you signed in on the Bridge. The relay matches the app to your laptop or desktop based on that account.
2. Wait for the Bridge
If the Bridge is online, Sesori automatically loads your project list.
If the Bridge is offline, Sesori shows a bridge-offline state. Start sesori-bridge on your laptop or desktop and the app will recover automatically.
Using OpenCode web alongside Sesori? If you want the OpenCode web interface and Sesori to stay in sync, start OpenCode web first (opencode web), then launch the Bridge with auto-start disabled and pointed at the web interface's port:
Replace 4096 with the port OpenCode web printed. Make sure workspaces are enabled in the OpenCode web interface so both surfaces share the same sessions and project state. See Connect to an existing OpenCode server for the full walkthrough.
3. Choose your assistant
If the Bridge detects more than one assistant, you'll see a Coding tool picker when creating a new session. Tap it to select which assistant handles that session. Support for additional assistants beyond OpenCode, Codex, and Cursor is in the works.
To check which assistants are available and their setup status, open Settings → Harnesses in the app. You can also reach the same screen from the Coding tool picker itself.
Each assistant shows a Setup status — Ready, Runtime missing, Authentication required, Unavailable, Not inspected, or Unknown — and, once it's ready, a Runtime status. From there you can enable or disable an assistant, refresh its setup, and restart it.
4. Open a project
A project is a repository or a folder you want to work on — basically the directory you'd cd into on your machine. Projects come from your assistant. Tap a project to see its sessions.
If you don't see a project, open that folder in your assistant on your machine first, then refresh Sesori.
5. Open or create a session
A session is a way to work on a task inside a project, either one at a time or several at once.
You can create multiple sessions per project. When you create one, a Dedicated workspace toggle gives that session its own copy of your project files, so two sessions can change the same file at the same time without conflicting, and Sesori can show clean file changes per session before you commit.
It's on by default. Turn it off to run the session directly against your working copy.
For Git users: under the hood, this uses Git worktrees. The toggle only appears for Git projects that have at least one commit — anywhere else, sessions run against your working copy.
Tap an existing session, or tap New session to start one from the app.
Next
Now let's look at what's inside the app.
Last updated
Was this helpful?