Docs: document nodes status

main
Peter Steinberger 2025-12-18 00:37:40 +00:00
parent 99325040f8
commit 1a2d39bdf9
4 changed files with 7 additions and 6 deletions

View File

@ -124,7 +124,7 @@ Iris is an internal/prototype iOS app that connects as a **remote node**:
- **Voice trigger:** forwards transcripts into the Gateway (agent runs + wakeups). - **Voice trigger:** forwards transcripts into the Gateway (agent runs + wakeups).
- **Canvas screen:** a WKWebView + `<canvas>` surface the agent can control (via `screen.eval` / `screen.snapshot` over `node.invoke`). - **Canvas screen:** a WKWebView + `<canvas>` surface the agent can control (via `screen.eval` / `screen.snapshot` over `node.invoke`).
- **Discovery + pairing:** finds the bridge via Bonjour (`_clawdis-bridge._tcp`) and uses Gateway-owned pairing (`clawdis nodes pending|approve`). - **Discovery + pairing:** finds the bridge via Bonjour (`_clawdis-bridge._tcp`) and uses Gateway-owned pairing (`clawdis nodes pending|approve`); `clawdis nodes status` shows paired nodes + capabilities.
Runbook: `docs/ios/connect.md` Runbook: `docs/ios/connect.md`
@ -201,7 +201,7 @@ Bot-mode support (grammY only) shares the same `main` session as WhatsApp/WebCha
| `clawdis gateway health|status|send|agent|call` | Gateway WS clients; assume a running gateway. | | `clawdis gateway health|status|send|agent|call` | Gateway WS clients; assume a running gateway. |
| `clawdis wake` | Enqueue a system event and optionally trigger a heartbeat via the Gateway. | | `clawdis wake` | Enqueue a system event and optionally trigger a heartbeat via the Gateway. |
| `clawdis cron ...` | Manage scheduled jobs (via Gateway). | | `clawdis cron ...` | Manage scheduled jobs (via Gateway). |
| `clawdis nodes ...` | Manage Gateway-owned node pairing. | | `clawdis nodes ...` | Manage nodes (pairing + status) via the Gateway. |
| `clawdis status` | Web session health + session store summary | | `clawdis status` | Web session health + session store summary |
| `clawdis health` | Reports cached provider state from the running gateway. | | `clawdis health` | Reports cached provider state from the running gateway. |
| `clawdis webchat` | Start the loopback-only WebChat HTTP server | | `clawdis webchat` | Start the loopback-only WebChat HTTP server |

View File

@ -82,9 +82,9 @@ Pairing details: `docs/gateway/pairing.md`.
## 5) Verify the node is connected ## 5) Verify the node is connected
- Via nodes list: - Via nodes status:
```bash ```bash
clawdis nodes list clawdis nodes status
``` ```
- Via Gateway: - Via Gateway:
```bash ```bash

View File

@ -70,6 +70,7 @@ CLI must be able to fully operate without any GUI:
- `clawdis nodes pending` - `clawdis nodes pending`
- `clawdis nodes approve <requestId>` - `clawdis nodes approve <requestId>`
- `clawdis nodes reject <requestId>` - `clawdis nodes reject <requestId>`
- `clawdis nodes status` (paired nodes + connection status/capabilities)
Optional interactive helper: Optional interactive helper:
- `clawdis nodes watch` (subscribe to `node.pair.requested` and prompt in-place) - `clawdis nodes watch` (subscribe to `node.pair.requested` and prompt in-place)

View File

@ -101,9 +101,9 @@ Pairing details: `docs/gateway/pairing.md`.
## 5) Verify the node is connected ## 5) Verify the node is connected
- In the macOS app: **Instances** tab should show something like `iOS Node (...)`. - In the macOS app: **Instances** tab should show something like `iOS Node (...)`.
- Via nodes list (paired + connected): - Via nodes status (paired + connected):
```bash ```bash
clawdis nodes list clawdis nodes status
``` ```
- Via Gateway (paired + connected): - Via Gateway (paired + connected):
```bash ```bash