openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@b277eac656

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-26 04:03:59 +00:00
parent e84da640cb
commit a260be57de
3 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "9ed11d6c49d800075cf5e1e923c28826942a77c6",
"syncedAt": "2026-04-26T04:01:15.793Z"
"sha": "b277eac656082954174def3a07c3b5df4481a943",
"syncedAt": "2026-04-26T04:02:33.696Z"
}

2
docs/gateway/remote.md
View File

@ -98,6 +98,8 @@ You can persist a remote target so CLI commands use it by default:
```
When the gateway is loopback-only, keep the URL at `ws://127.0.0.1:18789` and open the SSH tunnel first.
In the macOS app’s SSH tunnel transport, discovered gateway hostnames belong in
`gateway.remote.sshTarget`; `gateway.remote.url` remains the local tunnel URL.
## Credential precedence

5
docs/platforms/mac/remote.md
View File

@ -22,6 +22,11 @@ Remote mode supports two transports:
- **SSH tunnel** (default): Uses `ssh -N -L ...` to forward the gateway port to localhost. The gateway will see the node’s IP as `127.0.0.1` because the tunnel is loopback.
- **Direct (ws/wss)**: Connects straight to the gateway URL. The gateway sees the real client IP.
In SSH tunnel mode, discovered LAN/tailnet hostnames are saved as
`gateway.remote.sshTarget`. The app keeps `gateway.remote.url` on the local
tunnel endpoint, for example `ws://127.0.0.1:18789`, so CLI, Web Chat, and
browser automation all use the same safe loopback transport.
## Prereqs on the remote host
1. Install Node + pnpm and build/install the OpenClaw CLI (`pnpm install && pnpm build && pnpm link --global`).