Repository navigation
[FEATURE]:Document Portal as an optional HTTPS tunnel for OpenCode Web #53922
Description
Activity
Thanks for the proposal! You're suggesting the docs show how to put
opencode webbehind Portal, so a local instance can be reached over HTTPS from a phone or another computer while OpenCode keeps handling authentication throughOPENCODE_SERVER_PASSWORD. You'd also like to explore showing the tunnel URL or a QR code in the web UI later.Maintainers will consider whether and how to document this, for example as a general section on remote access through a reverse tunnel. I'd suggest waiting for their feedback before opening a PR.
Related issues:
- qrcode or generic "hook" in web mode for fast mobile access/qr codes/ngrok #10549: earlier (closed) request for a QR code / hook / ngrok-style setup in web mode for quick mobile access. It overlaps with your Phase 2.
- Web UI over plain HTTP: sessions appear empty / missing because crypto.subtle and crypto.randomUUID are unavailable on insecure origins #46662: the web UI misbehaves over plain HTTP because secure-context APIs are missing. This is relevant to the HTTPS / secure-context checks you mention.
- [FEATURE]: OpenCode Remote Control #47692: broader request for OpenCode remote control.
Metadata
Metadata
Assignees
Labels
No labels
Feature hasn't been suggested before.
Describe the enhancement you want to request
Summary
I'd like to propose adding Portal as an optional remote-access method for
opencode web.Portal is an MIT-licensed, self-hostable reverse tunnel that provides public HTTPS access to localhost without requiring an account, personal domain, or inbound port forwarding.
Motivation
OpenCode already provides a browser interface with configurable ports and HTTP Basic authentication.
Portal could make it easier to access a local OpenCode instance from a phone or another computer while keeping the server bound to
127.0.0.1.Proposed integration
Phase 1 — Documentation only
Document a minimal setup:
In another terminal:
Portal provides a public HTTPS URL, while OpenCode retains responsibility for authentication.
Before publishing, the example should be verified for Basic Auth, API requests, event streaming, browser Origin/CORS behavior, and secure-context functionality.
Phase 2 — Optional native integration
If there is interest, consider exposing the Portal URL or QR code in OpenCode's web interface.
This would remain entirely optional, without introducing a mandatory runtime dependency.
Previous integration
A similar documentation-first integration was recently merged into herdr-web-ui #229.
I'm maintaining Portal and would be happy to prepare and validate a documentation PR if this sounds useful.
The existing authentication model and remote-access options would remain unchanged.