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

docs: unify ws protocol + platform guides

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-19 08:54:21 +00:00
parent 66193dab92
commit 35e7c62e78
6 changed files with 120 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
docs/gateway/bridge-protocol.md
View File

@@ -1,18 +1,17 @@
---
summary: "Bridge protocol (nodes): TCP JSONL, pairing, scoped RPC"
summary: "Bridge protocol (legacy nodes): TCP JSONL, pairing, scoped RPC"
read_when:
- Building or debugging node clients (iOS/Android/macOS node mode)
- Investigating pairing or bridge auth failures
- Auditing the node surface exposed by the gateway
---
# Bridge protocol (Node transport)
# Bridge protocol (legacy node transport)
The Bridge protocol is a **narrow, authenticated** transport for nodes
(iOS/Android/macOS node mode). It keeps the Gateway WS control plane loopback‑only
and exposes only a scoped set of methods for nodes.
The Bridge protocol is a **legacy** node transport (TCP JSONL). New node clients
should use the unified Gateway WebSocket protocol instead.
If you are building an operator client (CLI, web UI, automations), use the
If you are building an operator or node client, use the
[Gateway protocol](/gateway/protocol).
## Why we have both