OMP Session Gateway
Decision guide
Keep the terminal, or move the work to a browser?
Start with the workflow you want to keep. A directory for running terminal sessions, a browser-hosted workspace, and remote shell access solve different problems.
Keep your running OMP terminal sessions
OMP Session Gateway puts participating interactive sessions on one private mobile page and opens View or Control in OMP's existing encrypted collaboration client. The gateway keeps bounded metadata, not transcripts.
Stock OMP ≥18.1.20 supplies the native registry and controller. No fork, custom OMP build, or gateway-specific OMP plugin is needed. The gateway remains a separate companion.
One-time setup: install the gateway with Bun 1.4.0, enable
collab.autoStart, and configure TUN-mode Tailscale Serve with an exact user allowlist
and Funnel disabled. Then start sessions with plain omp — no per-session link copying.
Setup guide.
Choose a different workflow
- A browser-hosted OMP workspace: omp-deck embeds the OMP SDK in-process and shares OMP's session/auth store. Choose it for persistent browser sessions and the work around chat, such as kanban, routines, and an inbox; its README says the OMP CLI need not be installed separately. Sources: README, package.
- Agent web chat, sharing, or a remote terminal:
oh-my-portal provides skills for several CLI
agents over Portal tunnels. OMP web chat uses RPC; its optional
omp-collabskill also shares a live session through OMP's own collaboration path. Choose the surface you need rather than treating it as a terminal-session directory. Sources: README, package. - A browser/mobile workspace for other coding CLIs: CloudCLI (claudecodeui) advertises Claude Code, Cursor CLI, and Codex in its README, with self-hosted and hosted options. That README does not advertise OMP support; do not assume OMP compatibility from a similar interface. Sources: README, package.
- A dashboard alongside the pi terminal: pi-agent-dashboard mirrors pi sessions through a bridge extension and supports browser interaction. Its README explicitly says Oh My Pi is not supported; pi and OMP are different integration targets. Sources: README, package.
Evidence and limits
The latest stable gateway release is published from a qualified signed candidate. Its minimum OMP version is an integration contract, not evidence that every later version or platform was tested. Qualification covers the exact OMP 18.3.0/Bun 1.4.0 Debian/macOS/Windows Server 2025/Pixel matrix, background Web Push on the Pixel, and a 1,800-second relay check, not eight hours. Linux, macOS, and Windows hosts and the Chromium, Firefox, and WebKit browser engines are supported and tested in CI, which is not qualification. Specialized attention, branch/resume, and broader host/browser combinations remain unqualified. The status page and release ledger retain the per-release evidence.
Primary READMEs and package metadata checked 2026-09-14. This is a workflow comparison, not a hands-on interoperability test or a security assessment of the other projects. Their scope can change; follow the source links before deciding. The upstream discussion provides further context.