Docs: add canvas host usage
This commit is contained in:
@@ -42,6 +42,7 @@ Clawdis already uses:
|
||||
For the clawd browser-control server, use “family” ports:
|
||||
- Browser control HTTP API: `18791` (bridge + 1)
|
||||
- Browser CDP/debugging port: `18792` (control + 1)
|
||||
- Canvas host HTTP (optional): `18793` (next free port; see `docs/configuration.md`)
|
||||
|
||||
The user usually only configures the **control URL** (port `18791`). CDP is an internal detail.
|
||||
|
||||
|
||||
@@ -10,6 +10,8 @@ read_when:
|
||||
|
||||
Status: draft spec · Date: 2025-12-12
|
||||
|
||||
Note: for iOS/Android nodes that should render agent-edited HTML/CSS/JS over the network, prefer the Gateway `canvasHost` (serves `~/clawd/canvas` over LAN/tailnet with live reload). This doc focuses on the macOS in-app canvas panel. See `docs/configuration.md`.
|
||||
|
||||
Clawdis can embed an agent-controlled “visual workspace” panel (“Canvas”) inside the macOS app using `WKWebView`, served via a **custom URL scheme** (no loopback HTTP port required).
|
||||
|
||||
This is designed for:
|
||||
|
||||
Reference in New Issue
Block a user