docs(guide): add remote-orchestration page (SSH/frpc reverse tunnel)#1337
Merged
docs(guide): add remote-orchestration page (SSH/frpc reverse tunnel)#1337
Conversation
Document the pattern for running opencli on a remote machine while keeping the daemon and Chrome on the local machine. Reverse-tunnel local 19825 back to the remote (via SSH -R or frp) so the remote opencli still talks to its own loopback and the daemon never leaves localhost. Captures the rationale we landed on after reviewing #636: native extension-to-remote-daemon support is deferred until the daemon protocol gains authentication; in the meantime this is the safe, zero-code path that achieves the same outcome.
13 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/guide/remote-orchestration.mddocumenting how to runopenclifrom a remote machine while keeping the browser, extension, and daemon on the local laptop. Uses SSH-R(recommended) or frp reverse TCP proxy to expose the local daemon to the remote's loopback — the daemon itself never leaves localhost.browser-bridge.mdso users discovering the bridge can find the remote story.Why
This is the conclusion of the #636 review. #636 proposed letting the extension popup connect to a remote daemon — that pushes the daemon's WebSocket protocol (which has no auth) onto an external network. The reverse-tunnel pattern reaches the same outcome (remote orchestration + local browser session + local IP) with zero code changes and without weakening the daemon's localhost-only security model.
This doc gives users that path explicitly so we can close #636 with a meaningful redirect, and it captures the rationale (defer extension-side remote support until daemon auth exists) so future contributors don't re-litigate the same design.
Test plan