> For the complete documentation index, see [llms.txt](https://docs.sesori.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sesori.com/get-started/quickstart.md).

# Quickstart

Six steps to your first remote OpenCode session.

{% hint style="info" %}
**New to the terminal?** A couple of these steps need you to run commands in your laptop's Terminal app. If that sounds new, ask a developer friend or [reach out to us](mailto:hello@sesori.com) — we'll help you get set up.
{% endhint %}

## Before you start

You'll need:

* A GitHub account to sign in to Sesori.
* A laptop or desktop where you can run terminal commands.
* An AI provider subscription or API key (see step 2).

## 1. Install OpenCode

OpenCode is the AI coding engine Sesori connects to. Install it on your laptop or desktop:

{% hint style="info" %}
**On Windows, use WSL.** Install OpenCode inside your WSL terminal, then run the rest of this guide in that same WSL terminal — including installing and running `sesori-bridge`.
{% endhint %}

```bash
curl -fsSL https://opencode.ai/install | bash
```

Confirm it's installed by checking the version:

```bash
opencode -v
```

More details: [Prerequisites](/setup/prepare-opencode.md)

## 2. Connect your AI provider

Run the following to authenticate and connect your AI subscriptions or API keys:

```bash
opencode auth login
```

OpenCode supports all popular options including Codex/GPT subscriptions, KimiCode, Google Gemini, Anthropic API Key, and more. If you don't have a subscription yet, we recommend starting with either of:

* **OpenAI** — $20/month GPT subscription
* **OpenCode Go** — $5 first month, $10 thereafter

## 3. Install the Sesori Bridge

The **Sesori Bridge** is a small command-line tool that connects the Sesori app to OpenCode. Pick the tab for your operating system:

{% tabs %}
{% tab title="macOS / Linux" %}

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

{% endtab %}

{% tab title="Windows" %}
Run this in PowerShell:

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

{% hint style="info" %}
**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:

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

{% endhint %}
{% endtab %}
{% endtabs %}

More details: [Set Up Sesori](/setup/set-up-the-bridge.md)

## 4. Start the Bridge and sign in

Run the Bridge in your terminal:

```bash
sesori-bridge
```

When prompted, sign in with **GitHub**. Other sign-in options are currently under development and may not work as expected.

By default, `sesori-bridge` starts and manages its own local OpenCode server, so everything you do happens through the Sesori app on your phone.

{% hint style="warning" %}
**Keep this terminal window open.** Because everything is end-to-end encrypted and runs locally on your machine, your phone can only connect while your desktop is running and `sesori-bridge` is active in a terminal window. If you close the terminal, the connection is lost — just run `sesori-bridge` again to reconnect.
{% endhint %}

{% hint style="info" %}
**Want to use the OpenCode web interface alongside Sesori?** You can run both in sync. Start the OpenCode web interface first:

```bash
opencode web
```

Note the port it prints (for example, `4096`). Then start the Bridge against that same server with auto-start disabled:

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

Replace `4096` with the port OpenCode web is using. With this setup, Sesori and OpenCode web stay fully in sync — what you see in one shows up in the other.

**Enable workspaces in the OpenCode web interface** so both surfaces share the same sessions and project state. See [Connect to an existing OpenCode server](/setup/set-up-the-bridge.md#connect-to-an-existing-opencode-server) for the full walkthrough.
{% endhint %}

## 5. Install Sesori on your phone

**iPhone:** Install Sesori from the [App Store](https://apps.apple.com/app/sesori/id6760642500).

**Android:** Install Sesori from [Google Play](https://play.google.com/store/apps/details?id=com.sesori.app).

More details: [Install the App](/setup/install-the-app.md)

## 6. Open Sesori and connect

Open the Sesori app and sign in with the **same GitHub account** you used for the Bridge. If the Bridge is running on your machine, Sesori takes you straight to your project list.

More details: [Connect to OpenCode](/setup/connect-to-opencode.md)

## That's it

Tap a project, create or open a session, and send a prompt. You can type, use voice input, choose an agent/model, answer pending questions, and stop a running task from Sesori.

{% hint style="success" %}
**Stuck?** Check [Troubleshooting](/help/troubleshooting.md) — most setup issues have a known answer.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sesori.com/get-started/quickstart.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.