Skip to content

docs(remote): explain local gateway toggle prerequisite #4259

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bolichen97 merged 2 commits into from
Sep 10, 2026
+12 −1
Merged

docs(remote): explain local gateway toggle prerequisite #4259

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2bdc198
docs(remote): explain local gateway toggle prerequisite
adiarora06 Aug 18, 2026
161b7ee
docs(remote): correct client-only tunnel launch order
adiarora06 Sep 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/guides/remote-and-mobile.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -672,7 +672,18 @@ the browser holds, on the same clocks as [Session duration](#session-duration).
### Persistent SSH tunnel on macOS (LaunchAgent)

A terminal-held tunnel dies with the terminal. A LaunchAgent survives reboots
and reconnects after sleep. A ready-made plist is at
and reconnects after sleep.

If the desktop app should act only as a client for this remote gateway, turn off
**Settings → Developer → Gateway → Run a local gateway**, then quit the app so
its supervised gateway releases port 5476. Start the tunnel, verify the health
probe below, and only then reopen the app. Turning the switch off does not create
or supervise a tunnel; on the next launch the app expects a gateway to already
answer on port 5476. A connected entry on the Instances page does not satisfy
this requirement because those tunnels are supervised by the local gateway
itself and use separate loopback ports.

A ready-made plist is at
[`assets/com.kirocrew.tunnel.plist`](assets/com.kirocrew.tunnel.plist):

```bash
Expand Down
Loading