Document remote server network access setup#1872
Conversation
- Add desktop app instructions for enabling network access - Clarify headless CLI usage for remote connections
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
ApprovabilityVerdict: Approved Documentation-only change adding instructions for enabling network access to REMOTE.md. No code or runtime behavior is affected. You can customize Macroscope's approvability policy. Learn more. |
Summary
Settings→Connectionsflow for turning on local backend network access and generating a pairing link.t3 serveon a remote machine.Testing
Note
Low Risk
Documentation-only update that adds guidance for exposing the local backend via the desktop app and clarifies the CLI/headless remote workflow; no runtime or security logic changes.
Overview
Updates
REMOTE.mdto describe two supported ways to enable remote access: turning on Network access from the desktop app’s Settings → Connections (including where to find the reachable address and how to create a pairing link), or runningt3 servein a headless/SSH scenario.Also reframes the old headless server flow section as part of a broader Enabling Network Access guide.
Reviewed by Cursor Bugbot for commit 1955568. Bugbot is set up for automated code reviews on this repo. Configure here.
Note
Document network access setup for remote servers in REMOTE.md
Updates REMOTE.md to replace the 'Headless Server Flow' section with a new 'Enabling Network Access' section covering two options: using the desktop app's Settings → Connections UI (with network toggle, restart note, address display, and pairing link generation) or running
t3 serveon a headless/SSH remote machine without a GUI.Macroscope summarized 1955568.