Run OpenCode from your phone.

Sesori is the mobile client for OpenCode — a mobile AI coding tool that lets you steer OpenCode sessions from your phone. A lightweight open-source bridge runs on your laptop, attaches to your OpenCode session, and communicates with the mobile app through an end-to-end encrypted relay. Your code stays on your machine — the relay only sees opaque binary.

Sesori isn't a mobile IDE, cloud sandbox, or replacement for your desktop assistant. It is a mobile interface for your real dev environment: your laptop, your repo, your terminal, and your AI coding tool. Replit Mobile runs code in Replit's cloud; Cursor, Copilot, Claude Code, and similar tools are desktop assistants. Sesori sits beside them so you can review, steer, and continue sessions from your phone.

Sesori is focused on being a local-first mobile cockpit for AI coding sessions, not a cloud IDE. If you want direct side-by-side breakdowns, see our comparison pages and tool roundups in alternatives. We include where each tool is a better fit so you can choose based on your workflow, not marketing claims.

Yes. Sesori is designed for phone-first control of AI coding sessions that still run on your laptop. Start with our mobile Claude Code guide and then use the Sesori vs Claude Code remote control comparison if you are evaluating options.

Today, Sesori is the mobile client for OpenCode — full session control, voice input, and live diffs from your phone. The bridge CLI runs on macOS and Linux, and the mobile app is on iOS and Android. If you want a complete walkthrough, read our guide to OpenCode mobile.

Install the bridge CLI on your laptop. On macOS or Linux run curl -fsSL https://sesori.com/install.sh | bash; on Windows run irm https://sesori.com/install.ps1 | iex in PowerShell. Then run sesori-bridge. Download the Sesori app on iOS or Android and sign in with the same account — Apple, Google, GitHub, or email. The two pair automatically over the encrypted relay, even when your phone and laptop are on different networks. The bridge only needs to run when you want your phone to see the session. Full instructions are in the docs, and our guide to using OpenCode from your phone walks through the full OpenCode mobile workflow.

The Sesori app on your phone never talks to OpenCode directly — the bridge is what makes that work. A few reasons it has to live on your laptop:

• It exposes your local OpenCode session to your phone over the end-to-end encrypted relay (and handles the OAuth pairing flow), so you can connect from anywhere — not just the same network as your laptop.
• It delivers push notifications, so your phone pings you when a session needs input or a long-running task finishes.
• Its plugin architecture is how we add new assistants without shipping a new mobile app — OpenCode is supported today, with Codex, Cursor, Claude Code, and more in progress, all from the same Sesori app.
• It owns compatibility with new OpenCode versions, so we can ship bridge updates without waiting on Apple or Google review cycles.

All traffic between your phone and laptop is end-to-end encrypted (X25519 + XChaCha20-Poly1305). The relay only sees opaque binary — it can't read your code, prompts, or AI responses. Sesori retains account-level data, such as your sign-in identity and a small amount of routing metadata, while your account is active. Your code stays on your machine. If you want to use Sesori on a work laptop, check with your security team first, since some organizations restrict outbound relay connections.

If your phone is lost or stolen, sign out of the account used for Sesori or revoke that session from Apple, Google, or GitHub. For email sign-in, change your password to invalidate the session. To delete your account, use Delete account in the Sesori mobile app or email [email protected]. Because Sesori never stores your code, prompts, or AI responses, there is no message history to wipe — just account and routing metadata.

The bridge is open source and always will be. We'll share more about long-term pricing as the project matures, but the local-first, privacy-respecting core isn't going anywhere.