How Sesori works: the app, Bridge, relay, and encryption

How Sesori connects your phone to OpenCode, Codex, or Cursor through the Bridge, the relay, and end-to-end encryption.

Sesori connects your mobile app to the AI coding assistant running on your laptop or desktop — OpenCode, Codex, or Cursor — through the Sesori Bridge.

The assistant runs locally. Your projects, files, commands, and AI coding sessions stay on your machine.

The Bridge keeps the app connected. It starts or connects to the assistant, then forwards encrypted requests between the app and your machine.

The auth server handles sign-in. You sign in with GitHub, Google, Apple, or email, and it issues authentication tokens used by Sesori components.

The relay routes traffic. It uses those tokens to match the app and the Bridge automatically so Sesori can work from any network.

The relay can't read your data. Everything between your phone and your machine is end-to-end encrypted, using the same kind of modern cryptography that secure messaging apps rely on. The relay forwards traffic but can't see inside it.

We use X25519 for key exchange and XChaCha20-Poly1305 for the encrypted channel.

The four pieces

Piece	What it does	Where it runs
Sesori App	The mobile interface you interact with	iOS, Android (desktop coming)
Sesori Bridge CLI	Sits between the relay and the assistant	macOS, Linux, Windows
Sesori Auth Server	Handles sign-in flows and issues auth tokens	Cloud
Sesori Relay Server	Routes encrypted traffic between app and bridge	Cloud

The assistants themselves are separate, independent projects — Sesori just connects to them. The Bridge talks to each one through its own adapter, which is how new assistants get added without changing anything on your side. More are on the way.

Ready?

Quickstart