OMP Session Gateway
Decision guide
Reaching OMP sessions from a phone or browser
Remote access to live OMP sessions is an active ecosystem — see the upstream discussion that inventories these efforts. Every project below is excellent at a different job; this page exists to make the call fast and honest.
| Dimension | OMP Session Gateway | omp-deck | oh-my-portal | claudecodeui | pi-agent-dashboard |
|---|---|---|---|---|---|
| Primary job | Private directory, attention queue, and View/Control broker for already-running terminal OMP sessions | Web cockpit hosting its own OMP SDK sessions plus kanban, inbox, routines | Skills plugin exposing an agent from the phone: chat, terminal, sharing, notify | Web, desktop, and mobile UI for Claude Code, Cursor CLI, and Codex | Browser dashboard for pi agents; OMP not supported |
| Live terminal session discovery | Zero-touch: every interactive OMP process registers over authenticated local IPC | No terminal attach; sessions live in the deck | Per-surface skill setup; one OMP session shared at a time | Discovers session files; OMP proposal closed unmerged | pi only, via a bridge extension |
| Mobile surface | Android-first installable PWA, qualified on physical Pixel hardware | Responsive web app; Telegram bridge | Phone browser over encrypted Portal tunnels; ntfy push | Responsive design, hosted cloud, desktop apps | Mobile-friendly responsive layout |
| Exact OMP collab client reuse | Yes — opens OMP's own encrypted collab-web from pinned upstream source | No — own chat surface | No — own web chat; collab links reused separately | No — own transcript UI | No — own mirror protocol |
| Attention triage | Metadata-only FIFO Needs you queue with device-local Hold | Per-session plan approvals and queued prompts | Push when the agent needs you | Per-tool approvals in the UI | Interactive prompts inside a session view |
| Capability and secret handling | Memory-only capabilities fetched no-store after an explicit tap; never in logs, URLs, push, or storage | Provider keys in local files, masked in UI | Auth gate per surface; hosted link option end-to-end encrypted | Agent tools off by default | Provider keys in auth.json; paired bearer tokens |
| Remote path | Tailscale Serve over tailnet HTTPS only; loopback bind, TUN mode required, Funnel unsupported | Loopback default; you front it yourself | Portal relay tunnels terminating on your machine | Self-hosted on your network, or hosted cloud | Localhost; optional zrok public tunnel |
| Transcript storage | None — bounded metadata only; transcripts stay in OMP | Sessions persist and resume by design | Web chat keeps memory; terminal is live tmux | History persisted with resume | Mirrors live and historical pi sessions |
| Best fit | Make every current terminal OMP session safely reachable from a phone without copying links | A persistent browser cockpit that hosts sessions | Broad agent coverage and raw terminal access from a phone | Established multi-agent web UI with hosted distribution | The pi ecosystem, not OMP |
Source-verified against each project's public README and package metadata on 2026-08-21, with release metadata refreshed 2026-09-08. Capabilities change quickly — reverify before deciding. None of these projects, including this one, is affiliated with or endorsed by the Oh My Pi maintainers.
The one-sentence answer
If the desired change is narrowly “make every current terminal OMP session safely reachable from my phone without copying links,” OMP Session Gateway is the only option that attaches through OMP's own encrypted collaboration path and reuses the exact upstream client — at the cost of an exact OMP version pin plus the repository's controller/publisher patch. Choose one of the others for a broader browser-first working environment, multi-agent coverage, or raw terminal access.
Full table with sources: how it compares