ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-26 04:15:48 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs(gateway): define passive QR capability

Browse Source
This commit is contained in:
jesse-merhi
2026-08-17 14:06:46 +10:00
parent eee743c7dc
commit 0fed2b951c
2 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/gateway/clients.md
+7 -3
View File
@@ -140,9 +140,13 @@ System-agent setup is administrative. Request `operator.admin` when pairing the
device; every `openclaw.chat` call in this flow, including setup, polling,
cancellation, and reset, requires that scope.
Advertise `GATEWAY_CLIENT_CAPS.SYSTEM_AGENT_QR_CODE` only when the client can
render a QR image. A capable `openclaw.chat` session can then receive a QR
`step` through the same wizard-step contract used for other setup controls:
Advertise `GATEWAY_CLIENT_CAPS.SYSTEM_AGENT_QR_CODE` only when the client
implements the complete passive QR lifecycle: render and expire the image,
poll through `wizardSettling`, resume the same poll after a same-owner
reconnect, handle invalidation and reset, and scrub every QR reference after
completion, expiry, cancellation, or disconnect. Rendering alone is not
sufficient. A capable `openclaw.chat` session can then receive a QR `step`
through the same wizard-step contract used for other setup controls:
```json
{
packages/gateway-protocol/src/client-info.ts
+1
View File
@@ -86,6 +86,7 @@ export const GATEWAY_CLIENT_CAPS = {
RUN_TOOL_BINDINGS: "run-tool-bindings",
SESSION_SCOPED_EVENTS: "session-scoped-events",
PLUGIN_APPROVALS: "plugin-approvals",
/** Renders and securely retires passive QR steps, including polling and reconnect recovery. */
SYSTEM_AGENT_QR_CODE: "system-agent-qr-code",
TASK_SUGGESTIONS: "task-suggestions",
TERMINAL_OFFSET_SEQ: "terminal-offset-seq",