Expose OpenCode web for secure remote access #52
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Personal/nixos-configuration#52
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Make the OpenCode web interface reachable when I’m away from home, while keeping access tightly restricted.
Context
See OpenCode Web documentation. The web UI is served by the OpenCode server and is password-protected; the server listens on localhost by default. Pairing uses a one-time link that expires after five minutes, and the resulting browser session lasts 30 days. OpenCode also documents an OpenTunnel-based
opencode pair --remoteoption that exposes the server to the internet, with encrypted traffic and server-password authentication.Evaluate this native remote option against private Tailscale access (for example, Tailscale Serve rather than Funnel) before choosing an architecture. The fact that a remote option has password protection is not by itself a reason to expose it publicly; consider the tunnel provider, threat model, and whether private tailnet access can meet the need.
Scope
OPENCODE_PASSWORD, inject it through the repository’s secret-management approach; never commit the secret in plaintext.Acceptance criteria