BuzzbeeSCD/openchamber
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(cli): make connect-url --relay a full anywhere pairing link

Browse Source 
- --relay links now carry both routes: direct LAN plus relay fallback,
  matching the UI's Anywhere pairing; devices prefer the direct route
- pairing sessions created by the CLI are marked with usesRelay, and the
  server reconciles relay demand on a timer, so a headless instance
  brings the relay up on its own after connect-url --relay
- warn with LAN_UNREACHABLE when the link's direct route points at
  loopback and other devices cannot use it
- document the --relay flow and the --lan binding caveat in Connect a
  Device and Remote Instances across all locales
This commit is contained in:
Bohdan Triapitsyn
2026-07-10 18:29:15 +03:00
parent de92b8fef4
commit 6ec1797583
21 changed files with 182 additions and 87 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/docs/content/docs/connect-devices.mdx
+14 -2
View File
@@ -40,13 +40,25 @@ The same physical device keeps one entry even if it signs in again later — you
## Connect from the command line
If the server runs headless (no UI open), create a connection link from a terminal on that machine:
If the server runs headless (no UI open), create a connection link from a terminal on that machine.
For a device on the same network:
```bash
openchamber connect-url --port 3000 --qr
```
The printed link and QR code work exactly like the ones from the settings dialog.
For a device that should connect from **anywhere** — the equivalent of picking **Anywhere** in the dialog:
```bash
openchamber connect-url --relay --qr
```
A `--relay` link carries both routes, just like the dialog: the device connects directly over your local network when it can reach the server, and falls back to the [Private Relay](/private-relay/) when away. The relay starts on its own: a running instance picks the link up within a minute, a stopped one on its next launch.
> The direct route only works if the server actually listens on your network. By default OpenChamber listens on the machine itself only — start it with `--lan` to make it reachable over Wi-Fi. The command warns you (`[LAN_UNREACHABLE]`) when the link's direct route won't be usable from other devices; a `--relay` link still works then, just always through the relay.
The printed link and QR code work exactly like the ones from the settings dialog — single-use, expiring, revocable.
## Related