Set up the Sesori Bridge on macOS, Linux, or Windows

Install and run the Sesori Bridge CLI on macOS, Linux, or Windows to connect your phone to OpenCode, Codex, or Cursor.

Sesori is an ecosystem of two components:

• The Sesori Bridge — a small command-line tool that runs on your laptop or desktop. It signs in, starts or connects to your AI coding assistant (OpenCode, Codex, or Cursor), and keeps the Sesori app connected through the encrypted relay.
• The Sesori app — installed on your phone (or another computer) so you can drive your AI coding sessions from anywhere.

This page walks through the Bridge first, then points you to install the app.

Make sure the prerequisites are in place first. If your assistant doesn't run locally, the Bridge has nothing useful to connect to.

Using Windows with WSL? If you installed OpenCode in WSL, install and run sesori-bridge from that same WSL terminal so the Bridge can connect to the same local OpenCode instance.

1. Install the Bridge

The simplest way is to install the Bridge once, system-wide. Pick the tab for your operating system:

macOS / Linux

curl -fsSL https://sesori.com/install.sh | bash

Windows

Run this in PowerShell:

irm https://sesori.com/install.ps1 | iex

Windows PATH. The installer adds sesori-bridge to your PATH and refreshes the current PowerShell session, so the next step usually works right away. If sesori-bridge returns "command not found", open a new PowerShell window — or refresh PATH in this one:

$env:Path = [Environment]::GetEnvironmentVariable("Path","Machine") + ";" + [Environment]::GetEnvironmentVariable("Path","User")

This puts a sesori-bridge command on your PATH so you can run it from any terminal.

2. Run the Bridge

Open a terminal and run:

sesori-bridge

The first run will:

1. Show a terminal prompt asking you to choose a sign-in method. Select one and follow the prompts — your browser opens after you choose a provider.
2. Start or connect to your local AI coding assistant.
3. Register the Bridge with the Sesori relay.
4. Start listening for connections from the Sesori app.

You'll see something like:

Target [opencode]: http://127.0.0.1:4096

Your Sesori bridge is running

Install or open Sesori using the QR code or link below, then sign in with this same account.

Detected assistants

The Bridge detects installed assistants automatically on startup — OpenCode, Codex, and Cursor today, with Claude Code coming soon. You choose which one to use from the app. To see what the Bridge knows about, run:

sesori-bridge config plugins

This prints each assistant and whether it's enabled, for example:

Codex (codex): enabled
Cursor (cursor): enabled
OpenCode (opencode): enabled

You can enable or disable individual assistants with sesori-bridge config plugins enable <id> or sesori-bridge config plugins disable <id>.

Keep it running

The Bridge has to be running for Sesori to reach your assistant on your laptop or desktop.

Run it in the background. On macOS and Linux you can use nohup sesori-bridge &, tmux, or a launchd / systemd unit. Leaving it open in a terminal is the simplest option.

Verify

In the Sesori app, the bridge status indicator shows green when the Bridge is online. If it's red, the Bridge isn't running on your laptop or desktop.

Connect to an existing OpenCode server

By default, sesori-bridge starts and manages its own OpenCode server. If you'd like to use the OpenCode web interface alongside Sesori, you can run OpenCode yourself and tell the Bridge to attach to it instead — both interfaces then stay fully in sync.

First, start the OpenCode web interface:

opencode web

Note the port it prints (for example, 4096).

Enable workspaces in the OpenCode web interface. Sesori relies on workspaces to share sessions and project state with the web UI. Without workspaces enabled, the two interfaces won't stay in sync.

Then start the Bridge with auto-start disabled, pointing at that same port:

sesori-bridge --opencode-no-auto-start --opencode-port 4096

Replace 4096 with the port OpenCode web is using. The --opencode-no-auto-start flag requires --opencode-port — omitting the port raises an error. The Bridge will skip launching its own OpenCode server and connect to the one you already have running. From this point on, anything you do in Sesori shows up in OpenCode web, and vice versa.

3. Install and run the Sesori app

With the Bridge online, install the Sesori app on your phone (or another computer) and sign in with the same account you used for the Bridge.

👉 Install the App

Troubleshooting

"Port already in use" — Another copy of the Bridge is already running. Close the other one or use pkill sesori-bridge on macOS/Linux.

"Could not reach relay" — Check your internet connection. The Bridge needs outbound HTTPS (port 443) to the Sesori relay.

"Assistant not responding" — The Bridge couldn't start or reach your assistant. Confirm the assistant is installed and on your PATH, then restart the Bridge.

For more issues, see Troubleshooting.

Next

Now that the Bridge is running and the app is installed, connect them.

👉 Connect the App