58 lines
3.4 KiB
Markdown
58 lines
3.4 KiB
Markdown
---
|
||
summary: "macOS app flow for controlling a remote Clawdis gateway over SSH"
|
||
read_when:
|
||
- Setting up or debugging remote mac control
|
||
---
|
||
# Remote Clawdis (macOS ⇄ remote host)
|
||
|
||
Updated: 2025-12-08
|
||
|
||
This flow lets the macOS app act as a full remote control for a Clawdis gateway running on another host (e.g. a Mac Studio). All features—health checks, Voice Wake forwarding, and Web Chat—reuse the same remote SSH configuration from *Settings → General*.
|
||
|
||
## Modes
|
||
- **Local (this Mac)**: Everything runs on the laptop. No SSH involved.
|
||
- **Remote over SSH**: Clawdis commands are executed on the remote host. The mac app opens an SSH connection with `-o BatchMode` plus your chosen identity/key.
|
||
|
||
## Prereqs on the remote host
|
||
1) Install Node + pnpm and build/install the Clawdis CLI (`pnpm install && pnpm build && pnpm link --global`).
|
||
2) Ensure `clawdis` is on PATH for non-interactive shells (symlink into `/usr/local/bin` or `/opt/homebrew/bin` if needed).
|
||
3) Open SSH with key auth. We recommend **Tailscale** IPs for stable reachability off-LAN.
|
||
|
||
## macOS app setup
|
||
1) Open *Settings → General*.
|
||
2) Under **Clawdis runs**, pick **Remote over SSH** and set:
|
||
- **SSH target**: `user@host` (optional `:port`).
|
||
- If the gateway is on the same LAN and advertises Bonjour, pick it from the discovered list to auto-fill this field.
|
||
- **Identity file** (advanced): path to your key.
|
||
- **Project root** (advanced): remote checkout path used for commands.
|
||
- **CLI path** (advanced): optional path to a runnable `clawdis` entrypoint/binary (auto-filled when advertised).
|
||
3) Hit **Test remote**. Success indicates the remote `clawdis status --json` runs correctly. Failures usually mean PATH/CLI issues; exit 127 means the CLI isn’t found remotely.
|
||
4) Health checks and Web Chat will now run through this SSH tunnel automatically.
|
||
|
||
## Web Chat over SSH
|
||
- Web Chat connects to the gateway over the forwarded WebSocket control port (default 18789).
|
||
- There is no separate WebChat HTTP server anymore.
|
||
|
||
## Permissions
|
||
- The remote host needs the same TCC approvals as local (Automation, Accessibility, Screen Recording, Microphone, Speech Recognition, Notifications). Run onboarding on that machine to grant them once.
|
||
- Nodes advertise their permission state via `node.list` / `node.describe` so agents know what’s available.
|
||
|
||
## WhatsApp login flow (remote)
|
||
- Run `clawdis login --verbose` **on the remote host**. Scan the QR with WhatsApp on your phone.
|
||
- Re-run login on that host if auth expires. Health check will surface link problems.
|
||
|
||
## Troubleshooting
|
||
- **exit 127 / not found**: `clawdis` isn’t on PATH for non-login shells. Add it to `/etc/paths`, your shell rc, or symlink into `/usr/local/bin`/`/opt/homebrew/bin`.
|
||
- **Health probe failed**: check SSH reachability, PATH, and that Baileys is logged in (`clawdis status --json`).
|
||
- **Web Chat stuck**: confirm the gateway is running on the remote host and the forwarded port matches the gateway WS port; the UI requires a healthy WS connection.
|
||
- **Voice Wake**: trigger phrases are forwarded automatically in remote mode; no separate forwarder is needed.
|
||
|
||
## Notification sounds
|
||
Pick sounds per notification from scripts with `clawdis` and `node.invoke`, e.g.:
|
||
|
||
```bash
|
||
clawdis nodes notify --node <id> --title "Ping" --body "Remote gateway ready" --sound Glass
|
||
```
|
||
|
||
There is no global “default sound” toggle in the app anymore; callers choose a sound (or none) per request.
|