Native OMP integration · no fork required

Every live OMP session. One private mobile page.

Keep using Oh My Pi in your terminal. OMP Session Gateway works with stock OMP 18.1.20+ to put your collaboration-enabled sessions on one private page, on your phone or any modern browser. See which need attention, then tap View or Control to open OMP's own encrypted client — no QR scans, copied links, or per-session setup.

Stock OMP. One-time setup.
Enable collab.autoStart, install the gateway with Bun 1.4.0, and configure Tailscale Serve. Then start sessions with plain omp. No custom OMP build or gateway-specific OMP plugin. Use it from modern browsers, and install it as a PWA on platforms that support installation.

Latest stable release · Linux, macOS, and Windows hosts; Chrome, Edge, Firefox, and Safari, tested in CI · qualified on Debian/macOS hosts and a Pixel · exact matrix and limits · release evidence

Get started Download the stable release

Three-step product flow: discover every live OMP session automatically, triage the oldest request that needs attention, and open the exact encrypted OMP collaboration session with View or Control. — Captured from the built PWA and pinned collaboration client with seeded synthetic fixtures — no real sessions, hosts, accounts, or capabilities. This synthetic product demo is not release or attention qualification; capture provenance.

The founder-approved relay gate for mainline releases is 30 minutes, not eight hours: eight-hour endurance was not rerun or claimed, and residual prolonged-operation risk is accepted. No bounded-memory-growth claim is made. Windows is qualified as Windows Server 2025 x86-64, started at interactive logon. Other Windows versions are supported and CI-tested but not qualified. Background Web Push is qualified on the Pixel only, with force-stop and Doze outcomes recorded as observed variants, never guaranteed delivery. Specialized attention, branch/resume, and new media qualification remain outside the qualified core claim.

Use it when

You keep several interactive OMP sessions open in terminals and want each one reachable from your phone without a per-session command, QR scan, or link copy.
Your hosts are on a Tailscale tailnet and you can run Tailscale Serve with the TUN-mode client, Funnel disabled.
You want OMP's existing encrypted collab-web client, and you want collaboration links kept out of logs, URLs, notifications, and browser storage.

Use something else when

You want a browser-first cockpit that hosts its own sessions (omp-deck), raw terminal access from a phone across many agents (oh-my-portal), or an established multi-agent web UI (claudecodeui). The comparison is candid about this — the narrow job is what makes the recommendation credible.

OMP handles collaboration. The gateway makes it easy to find.

Stock OMP >= 18.1.20 publishes its own private host registry. Set collab.autoStart to view or control and start plain omp; no gateway-specific OMP build or publisher credential is needed. The loopback-only omp-gatewayd reads OMP discovery and queries each host for metadata. Tailscale Serve exposes the gateway listener to allowlisted tailnet identities over tailnet HTTPS, and the OMP Sessions PWA lists every live process as bounded metadata. Tapping View or Control fetches one no-store capability and hands off to OMP's end-to-end-encrypted relay; the gateway never stores or renders transcripts. Full detail: architecture · protocol · operations.

Fork-era release history

v0.3.0, approved 2026-09-09 with patched OMP v18.1.14, qualified Debian 13 x86-64, macOS 26.6.1 arm64, and Chrome 152 on Android 17 (Pixel 10 Pro). Its 28,800 s relay endurance and runtime-equivalent signed candidate v0.3.0-prealpha.3 remain historical evidence; none transfers to mainline. Crossing this architecture boundary requires the matching old CLI to uninstall the stopped gateway before reinstalling; do not import credential bundles. Gateway rollback does not switch OMP.