# Understand how Oysterun reaches your Host.

Overview

Trace the direct Client-to-Host path, the bounded role of Cloud, the install handoff, and the product surfaces verified today.

On this page

1. [How it works](#how-it-works)
1. [Architecture](#architecture)
1. [Install](#install)
1. [Features](#features)

## How it works

Oysterun runs a Host beside a supported Codex or Claude Code provider for the same operating-system user. The phone client and an ordinary website browser are two ways to reach that one Host identity; they open the same Session state instead of creating separate Hosts.

## Architecture

After a Client reaches the Host, Chat, Explorer and file access, websites, and Session control use the direct Client-to-Host path.

Oysterun Cloud separately supports bounded Host registration and notification delivery. Whether those support paths are used depends on the configured feature; they are distinct from direct product traffic.

## Install

Start on the Host machine: prepare and authenticate a supported Codex or Claude Code provider for the same operating-system user, install the current Oysterun package, verify the reported version, and complete guided Host setup.

[Follow Getting Started](/getting-started/en/index.html) for one current path from prerequisites to a Session you can return to.

## Features

The current product surface includes Sessions, Chat, Explorer, File Preview, websites, Scheduler, Mail, notifications, search, and Host lifecycle controls. A particular provider or Host configuration may expose only the surfaces it supports.

### Current maturity and roadmap

Oysterun is currently distributed as Beta software. The documentation records behavior verified today; it does not turn unshipped work or a roadmap date into a delivery promise.