let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: make remote host examples generic

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-12 02:11:33 +00:00
parent 4ced7b886e
commit d97c211e82
8 changed files with 14 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/gateway/configuration.md
View File

@@ -1726,7 +1726,7 @@ Notes:
### Local models (LM Studio) — recommended setup
Best current local setup (what we’re running): **MiniMax M2.1** on a beefy Mac Studio
Best current local setup (what we’re running): **MiniMax M2.1** on a powerful local machine
via **LM Studio** using the **Responses API**.
```json5

4
docs/gateway/remote-gateway-readme.md
View File

@@ -11,7 +11,7 @@ Clawdbot.app uses SSH tunneling to connect to a remote gateway. This guide shows
```
┌─────────────────────────────────────────────────────────────┐
│ MacBook │
│ Client Machine │
│ │
│ Clawdbot.app ──► ws://127.0.0.1:18789 (local port) │
│ │ │
@@ -150,4 +150,4 @@ launchctl bootout gui/$UID/com.clawdbot.ssh-tunnel
| `KeepAlive` | Automatically restarts tunnel if it crashes |
| `RunAtLoad` | Starts tunnel when the agent loads |
Clawdbot.app connects to `ws://127.0.0.1:18789` on your MacBook. The SSH tunnel forwards that connection to port 18789 on the remote machine where the Gateway is running.
Clawdbot.app connects to `ws://127.0.0.1:18789` on your client machine. The SSH tunnel forwards that connection to port 18789 on the remote machine where the Gateway is running.

2
docs/gateway/remote.md
View File

@@ -5,7 +5,7 @@ read_when:
---
# Remote access (SSH, tunnels, and tailnets)
This repo supports “remote over SSH” by keeping a single Gateway (the master) running on a host (e.g., your Mac Studio) and connecting clients to it.
This repo supports “remote over SSH” by keeping a single Gateway (the master) running on a dedicated host (desktop/server) and connecting clients to it.
- For **operators (you / the macOS app)**: SSH tunneling is the universal fallback.
- For **nodes (iOS/Android and future devices)**: prefer the Gateway **Bridge** when on the same LAN/tailnet (see [Discovery](/gateway/discovery)).