fix: route remote mac browser through node host

This commit is contained in:
Peter Steinberger
2026-04-26 05:25:13 +01:00
parent b8aef04ccd
commit ae45eebef1
10 changed files with 175 additions and 10 deletions

View File

@@ -25,7 +25,14 @@ Remote mode supports two transports:
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.
the local node-host service all use the same safe loopback transport.
Browser automation in remote mode is owned by the CLI node host, not by the
native macOS app node. The app starts the installed node host service when
possible; if you need browser control from that Mac, install/start it with
`openclaw node install ...` and `openclaw node start` (or run
`openclaw node run ...` in the foreground), then target that browser-capable
node.
## Prereqs on the remote host